Systems and methods for analyzing data in a non-destructive testing system

ABSTRACT

A collaboration system may include a non-destructive testing (NDT) inspection device that may communicate with at least one other computing device via a computing network. The computing network may communicatively couple a plurality of computing devices and the NDT inspection device may acquire inspection data, establish a communication connection to the at least one other computing device, and send the data to the at least one other computing device. There, the at least one other computing device may analyze the data. After the data is analyzed, the NDT inspection device may receive the analyzed data from the at least one other computing device.

BACKGROUND

The subject matter disclosed herein relates to non-destructive testing(NDT) systems, and particularly to systems and methods for sharing NDTdata with various parties.

Certain equipment and facilities, such as power generation equipment andfacilities, oil and gas equipment and facilities, aircraft equipment andfacilities, manufacturing equipment and facilities, and the like,include a plurality of interrelated systems, and processes. For example,power generation plants may include turbine systems and processes foroperating and maintaining the turbine systems. Likewise, oil and gasoperations may include carbonaceous fuel retrieval systems andprocessing equipment interconnected via pipelines. Similarly, aircraftsystems may include airplanes and maintenance hangars useful inmaintaining airworthiness and providing for maintenance support. Duringequipment operations, the equipment may degrade, encounter undesiredconditions such as corrosion, wear and tear, and so on, potentiallyaffecting overall equipment effectiveness. Certain inspectiontechniques, such as non-destructive inspection techniques ornon-destructive testing (NDT) techniques, may be used to detectundesired equipment conditions.

In a conventional NDT system, data may be shared with other NDToperators or personnel using portable memory devices, paper, of throughthe telephone. As such, the amount of time to share data between NDTpersonnel may depend largely on the speed at which the physical portablememory device is physically dispatched to its target. Accordingly, itwould be beneficial to improve the data sharing capabilities of the NDTsystem, for example, to more efficiently test and inspect a variety ofsystems and equipment.

BRIEF DESCRIPTION

Certain embodiments commensurate in scope with the originally claimedinvention are summarized below. These embodiments are not intended tolimit the scope of the claimed invention, but rather these embodimentsare intended only to provide a brief summary of possible forms of theinvention. Indeed, the invention may encompass a variety of forms thatmay be similar to or different from the embodiments set forth below.

In one embodiment, a collaboration system may include a non-destructivetesting (NDT) inspection device that may communicate with at least oneother computing device via a computing network. The computing networkmay communicatively couple a plurality of computing devices and the NDTinspection device may acquire inspection data, establish a communicationconnection to the at least one other computing device, and send the datato the at least one other computing device. There, the at least oneother computing device may analyze the data. After the data is analyzed,the NDT inspection device may receive the analyzed data from the atleast one other computing device.

In another embodiment, a computing device may include programinstructions that may receive data that has been acquired using one ormore non-destructive testing (NDT) inspection devices and identifymetadata associated with the data. The metadata may include informationthat corresponds to an asset being inspected using the one or more NDTinspection devices. After identifying the metadata, the computing devicemay organize the data based on the metadata and store the organized datain a memory.

In yet another embodiment, a non-transitory computer readable medium mayinclude instructions that may receive signals from one or moreinspection sensors as raw data, transmit the raw data at a first time toone or more computing devices for a data analysis, and receive the dataanalysis from the one or more computing devices at a second time.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the presentinvention will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 is a block diagram illustrating an embodiment of a distributednon-destructive testing (NDT) system, including a mobile device;

FIG. 2 is a block diagram illustrating further details of an embodimentof the distributed NDT system of FIG. 1;

FIG. 3 is a front view illustrating an embodiment of a borescope system14 communicatively coupled to the mobile device of FIG. 1 and a “cloud;”

FIG. 4 is an illustration of an embodiment of a pan-tilt-zoom (PTZ)camera system communicatively coupled to the mobile device of FIG. 1;

FIG. 5 is a flowchart illustrating an embodiment of a process useful inusing the distributed NDT system for planning, inspecting, analyzing,reporting, and sharing of data, such as inspection data;

FIG. 6 is a block diagram of an embodiment of information flow through awireless conduit;

FIG. 7 is a flowchart of an embodiment of a process for sharing datathat corresponds to the NDT system of FIG. 1, in accordance with aspectsof the present disclosure;

FIG. 8 is a flowchart of an embodiment of a process for presenting alist of recipients for shared data that corresponds to the NDT system ofFIG. 1, in accordance with aspects of the present disclosure;

FIG. 9 is a flowchart of an embodiment of a process for sharing datathat corresponds to the NDT system of FIG. 1 in real time or near realtime, in accordance with aspects of the present disclosure;

FIG. 10 is a flowchart of an embodiment of a process for automaticallysharing data that corresponds to the NDT system of FIG. 1, in accordancewith aspects of the present disclosure;

FIG. 11 is a block diagram of a collaboration system that corresponds tothe NDT system of FIG. 1, in accordance with aspects of the presentdisclosure;

FIG. 12 is a flowchart of an embodiment of a process for sharing adisplay and control of a computing device using the collaboration systemof FIG. 11, in accordance with aspects of the present disclosure;

FIG. 13 illustrates a flowchart of an embodiment of a process fordisabling certain functions of a device in the NDT system of FIG. 1using the collaboration system of FIG. 11, in accordance with aspects ofthe present disclosure;

FIG. 14 illustrates a flowchart of an embodiment of a process forproviding location aware data while inspecting a device in the NDTsystem of FIG. 1 using the collaboration system of FIG. 11, inaccordance with aspects of the present disclosure;

FIG. 15 illustrates a flowchart of an embodiment of a process forsending raw data that corresponds to the NDT system of FIG. 1 to acloud-computing device in the collaboration system of FIG. 11, inaccordance with aspects of the present disclosure;

FIG. 16 illustrates a flowchart of an embodiment of a process foranalyzing raw data that corresponds to the NDT system of FIG. 1 using acloud-computing device in the collaboration system of FIG. 11, inaccordance with aspects of the present disclosure;

FIG. 17 illustrates a flowchart of an embodiment of a process forsending data that corresponds to the NDT system of FIG. 1 to acloud-computing device in the collaboration system of FIG. 11, inaccordance with aspects of the present disclosure;

FIG. 18 illustrates a flowchart of an embodiment of a process fororganizing and analyzing data that corresponds to the NDT system of FIG.1 using a cloud-computing device in the collaboration system of FIG. 11,in accordance with aspects of the present disclosure;

FIG. 19 illustrates a flowchart of an embodiment of a process forimplementing a workflow for reviewing and/or analyzing data thatcorresponds to the NDT system of FIG. 1, in accordance with aspects ofthe present disclosure;

FIG. 20 illustrates a flowchart of an embodiment of a process forpreparing data that corresponds to the NDT system of FIG. 1 for analysisvia the collaboration system of FIG. 11, in accordance with aspects ofthe present disclosure; and

FIG. 21 illustrates a flowchart of an embodiment of a process foranalyzing data that corresponds to the NDT system of FIG. 1 for analysisvia the collaboration system of FIG. 11, in accordance with aspects ofthe present disclosure.

DETAILED DESCRIPTION

One or more specific embodiments will be described below. In an effortto provide a concise description of these embodiments, not all featuresof an actual implementation are described in the specification. Itshould be appreciated that in the development of any such actualimplementation, as in any engineering or design project, numerousimplementation-specific decisions must be made to achieve thedevelopers' specific goals, such as compliance with system-related andbusiness-related constraints, which may vary from one implementation toanother. Moreover, it should be appreciated that such a developmenteffort might be complex and time consuming, but would nevertheless be aroutine undertaking of design, fabrication, and manufacture for those ofordinary skill having the benefit of this disclosure.

When introducing elements of various embodiments of the presentinvention, the articles “a,” “an,” “the,” and “said” are intended tomean that there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

Embodiments of the present disclosure may apply to a variety ofinspection and testing techniques, including non-destructive testing(NDT) or inspection systems. In the NDT system, certain techniques suchas borescopic inspection, weld inspection, remote visual inspections,x-ray inspection, ultrasonic inspection, eddy current inspection, andthe like, may be used to analyze and detect a variety of conditions,including but not limited to corrosion, equipment wear and tear,cracking, leaks, and so on. The techniques described herein provide forimproved NDT systems suitable for borescopic inspection, remote visualinspections, x-ray inspection, ultrasonic inspection, and/or eddycurrent inspection, enabling enhanced data gathering, data analysis,inspection/testing processes, and NDT collaboration techniques.

The improved NDT systems described herein may include inspectionequipment using wireless conduits suitable for communicatively couplingthe inspection equipment to mobile devices, such as tablets, smartphones, and augmented reality eyeglasses; to computing devices, such asnotebooks, laptops, workstations, personal computers; and to “cloud”computing systems, such as cloud-based NDT ecosystems, cloud analytics,cloud-based collaboration and workflow systems, distributed computingsystems, expert systems and/or knowledge-based systems. Indeed, thetechniques described herein may provide for enhanced NDT data gathering,analysis, and data distribution, thus improving the detection ofundesired conditions, enhancing maintenance activities, and increasingreturns on investment (ROI) of facilities and equipment.

In one embodiment, a tablet may be communicatively coupled to the NDTinspection device (e.g., borescope, transportable pan-tilt-zoom camera,eddy current device, x-ray inspection device, ultrasonic inspectiondevice), such as a MENTOR™ NDT inspection device, available from GeneralElectric, Co., of Schenectady, N.Y., and used to provide, for example,enhanced wireless display capabilities, remote control, data analyticsand/or data communications to the NDT inspection device. While othermobile devices may be used, the use of the tablet is apt, however,insofar as the tablet may provide for a larger, higher resolutiondisplay, more powerful processing cores, an increased memory, andimproved battery life. Accordingly, the tablet may address certainissues, such as providing for improved visualization of data, improvingthe manipulatory control of the inspection device, and extendingcollaborative sharing to a plurality of external systems and entities.

Keeping the foregoing in mind, the present disclosure is directedtowards sharing data acquired from the NDT system and/or control ofapplications and/or devices in the NDT system. Generally, data generatedfrom the NDT system may be automatically distributed to various peopleor groups of people using techniques disclosed herein. Moreover, contentdisplayed by an application used to monitor and/or control devices inthe NDT system may be shared between individuals to create a virtualcollaborative environment for monitoring and controlling the devices inthe NDT system.

By way of introduction, and turning now to FIG. 1, the figure is a blockdiagram of an embodiment of distributed NDT system 10. In the depictedembodiment, the distributed NDT system 10 may include one or more NDTinspection devices 12. The NDT inspection devices 12 may be divided intoat least two categories. In one category, depicted in FIG. 1, the NDTinspection devices 12 may include devices suitable for visuallyinspecting a variety of equipment and environments. In another category,described in more detail with respect to FIG. 2 below, the NDT devices12 may include devices providing for alternatives to visual inspectionmodalities, such as x-ray inspection modalities, eddy current inspectionmodalities, and/or ultrasonic inspection modalities.

In the depicted first example category of FIG. 1, the NDT inspectiondevices 12 may include a borescope 14 having one or more processors 15and a memory 17, and a transportable pan-tilt-zoom (PTZ) camera 16having one or more processors 19 and a memory 21. In this first categoryof visual inspection devices, the bore scope 14 and PTZ camera 16 may beused to inspect, for example, a turbo machinery 18, and a facility orsite 20. As illustrated, the bore scope 14 and the PTZ camera 16 may becommunicatively coupled to a mobile device 22 also having one or moreprocessors 23 and a memory 25. The mobile device 22 may include, forexample, a tablet, a cell phone (e.g., smart phone), a notebook, alaptop, or any other mobile computing device. The use of a tablet,however, is apt insofar as the tablet provides for a good balancebetween screen size, weight, computing power, and battery life.Accordingly, in one embodiment, the mobile device 22 may be the tabletmentioned above, that provides for touchscreen input. The mobile device22 may be communicatively coupled to the NDT inspection devices 12, suchas the bore scope 14 and/or the PTZ camera 16, through a variety ofwireless or wired conduits. For example, the wireless conduits mayinclude WiFi (e.g., Institute of Electrical and Electronics Engineers[IEEE] 802.11X), cellular conduits (e.g., high speed packet access[HSPA], HSPA+, long term evolution [LTE], WiMax), near fieldcommunications (NFC), Bluetooth, personal area networks (PANs), and thelike. The wireless conduits may use a variety of communicationprotocols, such as TCP/IP, UDP, SCTP, socket layers, and so on. Incertain embodiments, the wireless or wired conduits may include securelayers, such as secure socket layers (SSL), virtual private network(VPN) layers, encrypted layers, challenge key authentication layers,token authentication layers, and so on. Wired conduits may includeproprietary cabling, RJ45 cabling, co-axial cables, fiber optic cables,and so on.

Additionally or alternatively, the mobile device 22 may becommunicatively coupled to the NDT inspection devices 12, such as theborescope 14 and/or the PTZ camera 16, through the “cloud” 24. Indeed,the mobile device 22 may use the cloud 24 computing and communicationstechniques (e.g., cloud-computing network), including but not limited toHTTP, HTTPS, TCP/IP, service oriented architecture (SOA) protocols(e.g., simple object access protocol [SOAP], web services descriptionlanguages (WSDLs)) to interface with the NDT inspection devices 12 fromany geographic location, including geographic locations remote from thephysical location about to undergo inspection. Further, in oneembodiment, the mobile device 22 may provide “hot spot” functionality inwhich mobile device 22 may provide wireless access point (WAP)functionality suitable for connecting the NDT inspection devices 12 toother systems in the cloud 24, or connected to the cloud 24, such as acomputing system 29 (e.g., computer, laptop, virtual machine(s) [VM],desktop, workstation). Accordingly, collaboration may be enhanced byproviding for multi-party workflows, data gathering, and data analysis.

For example, a borescope operator 26 may physically manipulate theborescope 14 at one location, while a mobile device operator 28 may usethe mobile device 22 to interface with and physically manipulate thebore scope 14 at a second location through remote control techniques.The second location may be proximate to the first location, orgeographically distant from the first location. Likewise, a cameraoperator 30 may physically operate the PTZ camera 16 at a thirdlocation, and the mobile device operator 28 may remote control PTZcamera 16 at a fourth location by using the mobile device 22. The fourthlocation may be proximate to the third location, or geographicallydistant from the third location. Any and all control actions performedby the operators 26 and 30 may be additionally performed by the operator28 through the mobile device 22. Additionally, the operator 28 maycommunicate with the operators 26 and/or 30 by using the devices 14, 16,and 22 through techniques such as voice over IP (VOIP), virtualwhiteboarding, text messages, and the like. By providing for remotecollaboration techniques between the operator 28 operator 26, andoperator 30, the techniques described herein may provide for enhancedworkflows and increase resource efficiencies. Indeed, nondestructivetesting processes may leverage the communicative coupling of the cloud24 with the mobile device 22, the NDT inspection devices 12, andexternal systems coupled to the cloud 24.

In one mode of operation, the mobile device 22 may be operated by thebore scope operator 26 and/or the camera operator 30 to leverage, forexample, a larger screen display, more powerful data processing, as wellas a variety of interface techniques provided by the mobile device 22,as described in more detail below. Indeed, the mobile device 22 may beoperated alongside or in tandem with the devices 14 and 16 by therespective operators 26 and 30. This enhanced flexibility provides forbetter utilization of resources, including human resources, and improvedinspection results.

Whether controlled by the operator 28, 26, and/or 30, the borescope 14and/or PTZ camera 16 may be used to visually inspect a wide variety ofequipment and facilities. For example, the bore scope 14 may be insertedinto a plurality of borescope ports and other locations of theturbomachinery 18, to provide for illumination and visual observationsof a number of components of the turbomachinery 18. In the depictedembodiment, the turbo machinery 18 is illustrated as a gas turbinesuitable for converting carbonaceous fuel into mechanical power.However, other equipment types may be inspected, including compressors,pumps, turbo expanders, wind turbines, hydroturbines, industrialequipment, and/or residential equipment. The turbomachinery 18 (e.g.,gas turbine) may include a variety of components that may be inspectedby the NDT inspection devices 12 described herein.

With the foregoing in mind, it may be beneficial to discuss certainturbomachinery 18 components that may be inspected by using theembodiments disclosed herein. For example, certain components of theturbomachinery 18 depicted in FIG. 1, may be inspected for corrosion,erosion, cracking, leaks, weld inspection, and so on. Mechanicalsystems, such as the turbomachinery 18, experience mechanical andthermal stresses during operating conditions, which may require periodicinspection of certain components. During operations of theturbomachinery 18, a fuel such as natural gas or syngas, may be routedto the turbomachinery 18 through one or more fuel nozzles 32 into acombustor 36. Air may enter the turbomachinery 18 through an air intakesection 38 and may be compressed by a compressor 34. The compressor 34may include a series of stages 40, 42, and 44 that compress the air.Each stage may include one or more sets of stationary vanes 46 andblades 48 that rotate to progressively increase the pressure to providecompressed air. The blades 48 may be attached to rotating wheels 50connected to a shaft 52. The compressed discharge air from thecompressor 34 may exit the compressor 34 through a diffuser section 56and may be directed into the combustor 36 to mix with the fuel. Forexample, the fuel nozzles 32 may inject a fuel-air mixture into thecombustor 36 in a suitable ratio for optimal combustion, emissions, fuelconsumption, and power output. In certain embodiments, theturbomachinery 18 may include multiple combustors 36 disposed in anannular arrangement. Each combustor 36 may direct hot combustion gasesinto a turbine 54.

As depicted, the turbine 54 includes three separate stages 60, 62, and64 surrounded by a casing 76. Each stage 60, 62, and 64 includes a setof blades or buckets 66 coupled to a respective rotor wheel 68, 70, and72, which are attached to a shaft 74. As the hot combustion gases causerotation of turbine blades 66, the shaft 74 rotates to drive thecompressor 34 and any other suitable load, such as an electricalgenerator. Eventually, the turbomachinery 18 diffuses and exhausts thecombustion gases through an exhaust section 80. Turbine components, suchas the nozzles 32, intake 38, compressor 34, vanes 46, blades 48, wheels50, shaft 52, diffuser 56, stages 60, 62, and 64, blades 66, shaft 74,casing 76, and exhaust 80, may use the disclosed embodiments, such asthe NDT inspection devices 12, to inspect and maintain said components.

Additionally, or alternatively, the PTZ camera 16 may be disposed atvarious locations around or inside of the turbo machinery 18, and usedto procure visual observations of these locations. The PTZ camera 16 mayadditionally include one or more lights suitable for illuminatingdesired locations, and may further include zoom, pan and tilt techniquesdescribed in more detail below with respect to FIG. 4, useful forderiving observations around in a variety of difficult to reach areas.The borescope 14 and/or the camera 16 may be additionally used toinspect the facilities 20, such as an oil and gas facility 20. Variousequipment such as oil and gas equipment 84, may be inspected visually byusing the borescope 14 and/or the PTZ camera 16. Advantageously,locations such as the interior of pipes or conduits 86, underwater (orunderfluid) locations 88, and difficult to observe locations such aslocations having curves or bends 90, may be visually inspected by usingthe mobile device 22 through the borescope 14 and/or PTZ camera 16.Accordingly, the mobile device operator 28 may more safely andefficiently inspect the equipment 18, 84 and locations 86, 88, and 90,and share observations in real-time or near real-time with locationgeographically distant from the inspection areas. It is to be understoodthat other NDT inspection devices 12 may be use the embodimentsdescribed herein, such as fiberscopes (e.g., articulating fiberscope,non-articulating fiberscope), and remotely operated vehicles (ROVs),including robotic pipe inspectors and robotic crawlers.

Turning now to FIG. 2, the figure is a block diagram of an embodiment ofthe distributed NDT system 10 depicting the second category of NDTinspection devices 12 that may be able to provide for alternativeinspection data to visual inspection data. For example, the secondcategory of NDT inspection devices 12 may include an eddy currentinspection device 92, an ultrasonic inspection device, such as anultrasonic flaw detector 94, and an x-ray inspection device, such adigital radiography device 96. The eddy current inspection device 92 mayinclude one or more processors 93 and a memory 95. Likewise, theultrasonic flaw detector 94 may include one or more processors 97 and amemory 104. Similarly, the digital radiography device 96 may include oneor more processors 101 and a memory 103. In operations, the eddy currentinspection device 92 may be operated by an eddy current operator 98, theultrasonic flaw detector 94 may be operated by an ultrasonic deviceoperator 100, and the digital radiography device 96 may be operated by aradiography operator 102.

As depicted, the eddy current inspection device 92, the ultrasonic flawdetector 94, and the digital radiography inspection device 96, may becommunicatively coupled to the mobile device 22 by using wired orwireless conduits, including the conduits mentioned above with respectto FIG. 1. Additionally, or alternatively, the devices 92, 94, and 96may be coupled to the mobile device 22 by using the cloud 24, forexample the borescope 14 may be connected to a cellular “hotspot,” anduse the hotspot to connect to one or more experts in borescopicinspection and analysis. Accordingly, the mobile device operator 28 mayremotely control various aspects of operations of the devices 92, 94,and 96 by using the mobile device 22, and may collaborate with theoperators 98, 100, and 102 through voice (e.g., voice over IP [VOIP]),data sharing (e.g., whiteboarding), providing data analytics, expertsupport and the like, as described in more detail herein.

Accordingly, it may be possible to enhance the visual observation ofvarious equipment, such as an aircraft system 104 and facilities 106,with x-ray observation modalities, ultrasonic observation modalities,and/or eddy current observation modalities. For example, the interiorand the walls of pipes 108 may be inspected for corrosion and/orerosion. Likewise, obstructions or undesired growth inside of the pipes108 may be detected by using the devices 92, 94, and/or 96. Similarly,fissures or cracks 110 disposed inside of certain ferrous or non-ferrousmaterial 112 may be observed. Additionally, the disposition andviability of parts 114 inserted inside of a component 116 may beverified. Indeed, by using the techniques described herein, improvedinspection of equipment and components 104, 108, 112 and 116 may beprovided. For example, the mobile device 22 may be used to interfacewith and provide remote control of the devices 14, 16, 92, 94, and 96.

FIG. 3 is a front view of the borescope 14 coupled to the mobile device22 and the cloud 24. Accordingly, the borescope 14 may provide data toany number of devices connected to the cloud 24 or inside the cloud 24.As mentioned above, the mobile device 22 may be used to receive datafrom the borescope 14, to remote control the borescope 14, or acombination thereof. Indeed, the techniques described herein enable, forexample, the communication of a variety of data from the borescope 14 tothe mobile device 22, including but not limited to images, video, andsensor measurements, such as temperature, pressure, flow, clearance(e.g., measurement between a stationary component and a rotarycomponent), and distance measurements. Likewise, the mobile device 22may communicate control instructions, reprogramming instructions,configuration instructions, and the like, as described in more detailbelow.

As depicted the borescope 14, includes an insertion tube 118 suitablefor insertion into a variety of location, such as inside of theturbomachinery 18, equipment 84, pipes or conduits 86, underwaterlocations 88, curves or bends 90, varies locations inside or outside ofthe aircraft system 104, the interior of pipe 108, and so on. Theinsertion tube 118 may include a head end section 120, an articulatingsection 122, and a conduit section 124. In the depicted embodiment, thehead end section 120 may include a camera 126, one or more lights 128(e.g., LEDs), and sensors 130. As mentioned above, the borescope'scamera 126 may provide images and video suitable for inspection. Thelights 128 may be used to provide for illumination when the head end 120is disposed in locations having low light or no light.

During use, the articulating section 122 may be controlled, for example,by the mobile device 22 and/or a physical joy stick 131 disposed on theborescope 14. The articulating sections 122 may steer or “bend” invarious dimensions. For example, the articulation section 122 may enablemovement of the head end 120 in an X-Y plane X-Z plane and/or Y-Z planeof the depicted XYZ axes 133. Indeed, the physical joystick 131 and/orthe mobile device 22 may both be used alone or in combination, toprovide control actions suitable for disposing the head end 120 at avariety of angles, such as the depicted angle α. In this manner, theborescope head end 120 may be positioned to visually inspect desiredlocations. The camera 126 may then capture, for example, a video 134,which may be displayed in a screen 135 of the borescope 14 and a screen137 of the mobile device 22, and may be recorded by the borescope 14and/or the mobile device 22. In one embodiment, the screens 135 and 137may be multi-touchscreens using capacitance techniques, resistivetechniques, infrared grid techniques, and the like, to detect the touchof a stylus and/or one or more human fingers. Additionally oralternatively, images and the video 134 may be transmitted into thecloud 24.

Other data, including but not limited to sensor 130 data, mayadditionally be communicated and/or recorded by the borescope 14. Thesensor 130 data may include temperature data, distance data, clearancedata (e.g., distance between a rotating and a stationary component),flow data, and so on. In certain embodiments, the borescope 14 mayinclude a plurality of replacement tips 136. For example, thereplacement tips 136 may include retrieval tips such as snares, magnetictips, gripper tips, and the like. The replacement tips 136 mayadditionally include cleaning and obstruction removal tools, such aswire brushes, wire cutters, and the like. The tips 136 may additionallyinclude tips having differing optical characteristics, such as focallength, stereoscopic views, 3-dimensional (3D) phase views, shadowviews, and so on. Additionally or alternatively, the head end 120 mayinclude a removable and replaceable head end 120. Accordingly, aplurality of head ends 120 may be provided at a variety of diameters,and the insertion tube 118 maybe disposed in a number of locationshaving openings from approximately one millimeter to ten millimeters ormore. Indeed, a wide variety of equipment and facilities may beinspected, and the data may be shared through the mobile device 22and/or the cloud 24.

FIG. 4 is a perspective view of an embodiment of the transportable PTZcamera 16 communicatively coupled to the mobile device 22 and to thecloud 24. As mentioned above, the mobile device 22 and/or the cloud 24may remotely manipulate the PTZ camera 16 to position the PTZ camera 16to view desired equipment and locations. In the depicted example, thePTZ camera 16 may be tilted and rotated about the Y-axis. For example,the PTZ camera 16 may be rotated at an angle β between approximately 0°to 180°, 0° to 270°, 0° to 360°, or more about the Y-axis. Likewise, thePTZ camera 16 may be tilted, for example, about the Y-X plane at anangle γ of approximately 0° to 100°, 0° to 120°, 0° to 150°, or morewith respect to the Y-Axis. Lights 138 may be similarly controlled, forexample, to active or deactivate, and to increase or decrease a level ofillumination (e.g., lux) to a desired value. Sensors 140, such as alaser rangefinder, may also be mounted onto the PTZ camera 16, suitablefor measuring distance to certain objects. Other sensors 140 may beused, including long-range temperature sensors (e.g., infraredtemperature sensors), pressure sensors, flow sensors, clearance sensors,and so on.

The PTZ camera 16 may be transported to a desired location, for example,by using a shaft 142. The shaft 142 enables the camera operator 30 tomove the camera and to position the camera, for example, inside oflocations 86, 108, underwater 88, into hazardous (e.g., hazmat)locations, and so on. Additionally, the shaft 142 may be used to morepermanently secure the PTZ camera 16 by mounting the shaft 142 onto apermanent or semi-permanent mount. In this manner, the PTZ camera 16 maybe transported and/or secured at a desired location. The PTZ camera 16may then transmit, for example by using wireless techniques, image data,video data, sensor 140 data, and the like, to the mobile device 22and/or cloud 24. Accordingly, data received from the PTZ camera 16 maybe remotely analyzed and used to determine the condition and suitabilityof operations for desired equipment and facilities. Indeed, thetechniques described herein may provide for a comprehensive inspectionand maintenance process suitable for planning, inspecting, analyzing,and/or sharing a variety of data by using the aforementioned devices 12,14, 16, 22, 92, 94, 96, and the cloud 24, as described in more detailbelow with respect to FIG. 5.

FIG. 5 is a flowchart of an embodiment of a process 150 suitable forplanning, inspecting, analyzing, and/or sharing a variety of data byusing the aforementioned devices 12, 14, 16, 22, 92, 94, 96, and thecloud 24. Indeed, the techniques described herein may use the devices12, 14, 16, 22, 92, 94, 96 to enable processes, such as the depictedprocess 150, to more efficiently support and maintain a variety ofequipment. In certain embodiments, the process 150 or portions of theprocess 150 may be included in non-transitory computer-readable mediastored in memory, such as the memory 17, 21, 25, 95, 99, 103 andexecutable by one or more processors, such as the processors 15, 19, 23,93, 97, 101.

In one example, the process 150 may plan (block 152) for inspection andmaintenance activities. Data acquired by using the devices 12, 14, 16,22, 42, 44, 46, an others, such as fleet data acquired from a fleet ofturbomachinery 18, from equipment users (e.g., aircraft 104 servicecompanies), and/or equipment manufacturers, may be used to plan (block152) maintenance and inspection activities, more efficient inspectionschedules for machinery, flag certain areas for a more detailedinspection, and so on. The process 150 may then enable the use of asingle mode or a multi-modal inspection (block 154) of desiredfacilities and equipment (e.g., turbomachinery 18). As mentioned above,the inspection (block 154) may use any one or more of the NDT inspectiondevices 12 (e.g., borescope 14, PTZ camera 16, eddy current inspectiondevice 92, ultrasonic flaw detector 94, digital radiography device 96),thus providing with one or more modes of inspection (e.g., visual,ultrasonic, eddy current, x-ray). In the depicted embodiment, the mobiledevice 22 may be used to remote control the NDT inspection devices 12,to analyze data communicated by the NDT inspection devices 12, toprovide for additional functionality not included in the NDT inspectiondevices 12 as described in more detail herein, to record data from theNDT inspection devices 12, and to guide the inspection (block 154), forexample, by using menu-driven inspection (MDI) techniques, among others.

Results of the inspection (block 154), may then be analyzed (block 156),for example, by using the NDT device 12, by transmitting inspection datato the cloud 24, by using the mobile device 22, or a combinationthereof. The analysis may include engineering analysis useful indetermining remaining life for the facilities and/or equipment, wear andtear, corrosion, erosion, and so forth. The analysis may additionallyinclude operations research (OR) analysis used to provide for moreefficient parts replacement schedules, maintenance schedules, equipmentutilization schedules, personnel usage schedules, new inspectionschedules, and so on. The analysis (block 156) may then be reported(block 158), resulting in one or more reports 159, including reportscreated in or by using the cloud 24, detailing the inspection andanalysis performed and results obtained. The reports 159 may then beshared (block 160), for example, by using the cloud 24, the mobiledevice 22, and other techniques, such as workflow sharing techniques. Inone embodiment, the process 150 may be iterative, thus, the process 150may iterate back to planning (block 152) after the sharing (block 160)of the reports 159. By providing for embodiments useful in using thedevices (e.g., 12, 14, 16, 22, 92, 94, 96) described herein to plan,inspect, analyze, report, and share data, the techniques describedherein may enable a more efficient inspection and maintenance of thefacilities 20, 106 and the equipment 18, 104. Indeed, the transfer ofmultiple categories of data may be provided, as described in more detailbelow with respect to FIG. 6.

FIG. 6 is a data flow diagram depicting an embodiment of the flow ofvarious data categories originating from the NDT inspection devices 12(e.g., devices 14, 16, 92, 94, 96) and transmitted to the mobile device22 and/or the cloud 24. As mentioned above, the NDT inspection devices12 may use a wireless conduit 162 to transmit the data. In oneembodiment, the wireless conduit 112 may include WiFi (e.g., 802.11X),cellular conduits (e.g., HSPA, HSPA+, LTE, WiMax), NFC, Bluetooth, PANs,and the like. The wireless conduit 162 may use a variety ofcommunication protocols, such as TCP/IP, UDP, SCTP, socket layers, andso on. In certain embodiments, the wireless conduit 162 may includesecure layers, such as SSL, VPN layers, encrypted layers, challenge keyauthentication layers, token authentication layers, and so on.Accordingly, an authorization data 164 may be used to provide any numberof authorization or login information suitable to pair or otherwiseauthenticate the NDT inspection device 12 to the mobile device 22 and/orthe cloud 24. Additionally, the wireless conduit 162 may dynamicallycompress data, depending on, for example, currently available bandwidthand latency. The mobile device 22 may then uncompress and display thedata. Compression/decompression techniques may include H.261, H.263,H.264, moving picture experts group (MPEG), MPEG-1, MPEG-2, MPEG-3,MPEG-4, DivX, and so on.

In certain modalities (e.g., visual modalities), images and video may becommunicated by using certain of the NDT inspection devices 12. Othermodalities may also send video, sensor data, and so on, related to orincluded in their respective screens. The NDT inspection device 12 may,in addition to capturing images, overlay certain data onto the image,resulting in a more informative view. For example, a borescope tip mapmay be overlaid on the video, showing an approximation of thedisposition of a borescope tip during insertion so as to guide theoperator 26 to more accurately position the borescope camera 126. Theoverlay tip map may include a grid having four quadrants, and the tip136 disposition may be displayed as dot in any portion or positioninside of the four quadrants. A variety of overlays may be provided, asdescribed in more detail below, including measurement overlays, menuoverlays, annotation overlays, and object identification overlays. Theimage and video data, such as the video 84, may then be displayed, withthe overlays generally displayed on top of the image and video data.

In one embodiment, the overlays, image, and video data may be “screenscraped” from the screen 135 and communicated as screen scrapping data166. The screen scrapping data 166 may then be displayed on the mobiledevice 22 and other display devices communicatively coupled to the cloud24. Advantageously, the screen scrapping data 166 may be more easilydisplayed. Indeed, because pixels may include both the image or videoand overlays in the same frame, the mobile device 22 may simply displaythe aforementioned pixels. However, providing the screen scraping datamay merge both the images with the overlays, and it may be beneficial toseparate the two (or more) data streams. For example, the separate datastreams (e.g., image or video stream, overlay stream) may be transmittedapproximately simultaneously, thus providing for faster datacommunications. Additionally, the data streams may be analyzedseparately, thus improving data inspection and analysis.

Accordingly, in one embodiment, the image data and overlays may beseparated into two or more data streams 168 and 170. The data stream 168may include only overlays, while the data stream 170 may include imagesor video. In one embodiment, the images or video 170 may be synchronizedwith the overlays 168 by using a synchronization signal 172. Forexample, the synchronization signal may include timing data suitable tomatch a frame of the data stream 170 with one or more data itemsincluded in the overlay stream 168. In yet another embodiment, nosynchronization data 172 data may be used. Instead, each frame or image170 may include a unique ID, and this unique ID may be matched to one ormore of the overlay data 168 and used to display the overlay data 168and the image data 170 together.

The overlay data 168 may include a tip map overlay. For example, a gridhaving four squares (e.g., quadrant grid) may be displayed, along with adot or circle representing a tip 136 position. This tip map may thusrepresent how the tip 136 is being inserted inside of an object. A firstquadrant (top right) may represent the tip 136 being inserted into a topright corner looking down axially into the object, a second quadrant(top left) may represent the tip 136 being inserted into a left rightcorner looking down axially, a third quadrant (bottom left) mayrepresent the tip 136 being inserted into a bottom left corner, and afourth quadrant (bottom right) may represent the tip 136 being insertedinto a bottom right corner. Accordingly, the borescope operator 26 maymore easily guide insertion of the tip 136.

The overlay data 168 may also include measurement overlays. For example,measurement such as length, point to line, depth, area, multi-segmentline, distance, skew, and circle gauge may be provided by enabling theuser to overlay one or more cursor crosses (e.g., “+”) on top of animage. In one embodiment a stereo probe measurement tip 136, or a shadowprobe measurement tip 136 may be provided, suitable for measurementsinside of objects, including stereoscopic measurements and/or byprojecting a shadow onto an object. By placing a plurality of cursoricons (e.g., cursor crosses) over an image, the measurements may bederived using stereoscopic techniques. For example, placing two cursorsicons may provide for a linear point-to-point measurement (e.g.,length). Placing three cursor icons may provide for a perpendiculardistance from a point to a line (e.g., point to line). Placing fourcursor icons may provide for a perpendicular distance between a surface(derived by using three cursors) and a point (the fourth cursor) aboveor below the surface (e.g., depth). Placing three or more cursors arounda feature or defect may then give an approximate area of the surfacecontained inside the cursors. Placing three or more cursors may alsoenable a length of a multi-segment line following each cursor.

Likewise, by projecting a shadow, the measurements may be derived basedon illumination and resulting shadows. Accordingly, by positioning theshadow across the measurement area, then placing two cursors as close aspossible to the shadow at furthermost points of a desired measurementmay result in the derivation of the distance between the points. Placingthe shadow across the measurement area, and then placing cursors atedges (e.g., illuminated edges) of the desired measurement areaapproximately to the center of a horizontal shadow may result in a skewmeasurement, otherwise defined as a linear (point-to-point) measurementon a surface that is not perpendicular to the probe 14 view. This may beuseful when a vertical shadow is not obtainable.

Similarly, positioning a shadow across the measurement area, and thenplacing one cursor on a raised surface and a second cursor on a recessedsurface may result in the derivation of depth, or a distance between asurface and a point above or below the surface. Positioning the shadownear the measurement area, and then placing a circle (e.g., circlecursor of user selectable diameter, also referred to as circle gauge)close to the shadow and over a defect may then derive the approximatediameter, circumference, and/or area of the defect.

Overlay data 168 may also include annotation data. For example, text andgraphics (e.g. arrow pointers, crosses, geometric shapes) may beoverlaid on top of an image to annotate certain features, such as“surface crack.” Additionally, audio may be captured by the NDTinspection device 12, and provided as an audio overlay. For example, avoice annotation, sounds of the equipment undergoing inspection, and soon, may be overlaid on an image or video as audio. The overlay data 168received by the mobile device 22 and/or cloud 24 may then be rendered bya variety of techniques. For example, HTML5 or other markup languagesmay be used to display the overlay data 168. In one embodiment, themobile device 22 and/or cloud 24 may provide for a first user interfacedifferent from a second user interface provided by the NDT device 12.Accordingly, the overlay data 168 may be simplified and only send basicinformation. For example, in the case of the tip map, the overlay data168 may simply include X and Y data correlative to the location of thetip, and the first user interface may then use the X and Y data tovisually display the tip on a grid.

Additionally sensor data 174 may be communicated. For example, data fromthe sensors 126, 140, and x-ray sensor data, eddy current sensor data,and the like may be communicated. In certain embodiments, the sensordata 174 may be synchronized with the overlay data 168, for example,overlay tip maps may be displayed alongside with temperatureinformation, pressure information, flow information, clearance, and soon. Likewise, the sensor data 174 may be displayed alongside the imageor video data 170.

In certain embodiments, force feedback or haptic feedback data 176 maybe communicated. The force feedback data 176 may include, for example,data related to the borescope 14 tip 136 abutting or contacting againsta structure, vibrations felt by the tip 136 or vibration sensors 126,force related to flows, temperatures, clearances, pressures, and thelike. The mobile device 22 may include, for example, a tactile layerhaving fluid-filled microchannels, which, based on the force feedbackdata 176, may alter fluid pressure and/or redirect fluid in response.Indeed, the techniques describe herein, may provide for responsesactuated by the mobile device 22 suitable for representing sensor data174 and other data in the conduit 162 as tactile forces.

The NDT devices 12 may additionally communicate position data 178. Forexample, the position data 178 may include locations of the NDT devices12 in relation to equipment 18, 104, and/or facilities 20, 106. Forexample, techniques such as indoor GPS, RFID, triangulation (e.g., WiFitriangulation, radio triangulation) may be used to determine theposition 178 of the devices 12. Object data 180 may include data relatedto the object under inspection. For example, the object data 180 mayinclude identifying information (e.g., serial numbers), observations onequipment condition, annotations (textual annotations, voiceannotations), and so on. Other types of data 182 may be used, includingbut not limited to menu-driven inspection data, which when used,provides a set of pre-defined “tags” that can be applied as textannotations and metadata. These tags may include location information(e.g., 1st stage HP compressor) or indications (e.g., foreign objectdamage) related to the object undergoing inspection. Other data 182 mayadditionally include remote file system data, in which the mobile device22 may view and manipulate files and file constructs (e.g., folders,subfolders) of data located in the memory 25 of the NDT inspectiondevice 12. Accordingly, files may be transferred to the mobile device 22and cloud 24, edited and transferred back into the memory 25. Bycommunicating the data 164-182 to the mobile device 22 and the cloud 24,the techniques described herein may enable a faster and more efficientprocess 150.

Keeping the foregoing in mind, FIG. 7 illustrates an embodiment of aprocess 200 for sharing data that corresponds to the NDT system 10, suchas the data depicted above with respect to FIG. 6. In certainembodiments, the process 200 or portions of the process 200 may beincluded in non-transitory computer-readable media stored in memory,such as the memory 15, 19, 23, 25, 93, 97, 101 and executable by one ormore processors, such as the processors 17, 21, 25, 95, 99, 103 and thecloud 24.

In one embodiment, an application containing computer instructionsexecutable by the mobile device 22, the NDT inspection devices 12,and/or the cloud 24 may be used to collect data that may be related tothe inspection of a piece of equipment (e.g., devices 12, 14, 16, 22,42, 44, 46) within the NDT system 10 or may be used to generate reports159 related to the NDT system 10. Although the process 200 depicts aparticular order in which the process 200 may be performed, it should benoted that the process 200 may also be performed in a different order.

At block 202, the application may receive an indication of data or atype of data that the mobile device operator 28 may designate as data ora type of data that will be shared. That is, the mobile device operator28 may select data or a type of data that will be shared as it becomesavailable or is generated by the application. In certain embodiments,the data or type of data may be related to an inspection 154 of somenon-destructive testing results of a piece of equipment. In certainembodiments, the indication of data or the type of data to be shared maybe embedded as part of a configuration for the application. That is, thedata or type of data to be shared may be pre-designated according to aworkflow associated with the respective inspection of the piece ofequipment. As such, the workflow and the application configuration maybe established and stored in a server or like device.

In addition to receiving the data or data that corresponds to the typeof data to be shared (e.g., data provided through conduit 162), theapplication, at block 204, may receive a sharing process or a format inwhich the data or type of data will be shared. The format in which datamay be shared may include, for example, sending an electronic-mail(e-mail) message, text message, report 159, or the like that describesor includes the data that is designated to be shared to one or morerecipients. Along with the sharing process or format, the applicationmay receive an indication of a template that may be used to present thedata. In this case, prior to sending the data, the application may applythe template, generate a report using the template, and send the report.The template and the use of the template may be embedded as part of theconfiguration for the application or pre-designated according to theworkflow as discussed above.

In certain embodiments, the application may upload the data to be sharedinto the cloud 24 such that other individuals may download the data.Additionally, along with uploading the data or data that corresponds tothe type of data to be shared, the application may send a message tovarious individuals, who may be interested in the uploaded data,indicating that the data has been uploaded.

At block 206, the application may receive one or more recipients for thedata to be shared. In certain embodiments, the NDT operator 28, 26, 30,98, 100, and/or 102 may specify one or more recipients for each dataand/or type of data received at block 202. The recipients may includeexperts or management personnel that may correspond to the data or typeof data, third party entities (e.g., maintenance service providers,manufacturers), regulatory entities (e.g., Federal AviationAdministration [FAA], Environmental Protection Agency [EPA], Departmentof Transportation [DOT]), federal and state entities, and so on. Incertain embodiments, the application may present a list of potentialrecipients on a display based on the data or type of data being shared.Additional details with regard to how the application presents this listwill be described below with reference to FIG. 8.

After receiving the recipients for each data or type of data, at block208, the application may retrieve the data that may correspond to thedata specified at block 202 from its memory, such as memory 25. In oneembodiment, the application may retrieve the data as the data is beinggenerated. That is, the application may automatically retrieve data thatis to be shared once the data has been saved in a memory, inapproximately real-time or near real-time.

At block 210, the application may send the data designated to be sharedat block 202 to respective recipient(s). The data may be sent accordingto the sharing method or format specified at block 204. As such, theapplication may modify or alter the data retrieved at block 208 and sendthe modified data to the recipients received at block 206.

In certain embodiments, each recipient may have a preferred format toreceive shared data. As such, when receiving the recipients at block206, the application may also receive a preferred process or format inwhich each recipient may receive data. In this case, the application maysend the data designated to be shared at block 202 to respectiverecipient(s) in a format that corresponds to the preferred method inwhich each respective recipient may specify to receive data. That is,the application may override or disregard the sharing method received atblock 204 and send the data as per the preferred method of therespective recipient.

As mentioned above, at block 206, the application may present a list ofpotential recipients on a display according to a process 220 depicted inFIG. 8. That is, the method 220 may provide additional details withregard to how the application may receive recipients for the data to beshared. For example, at block 222, the application may cross referencethe data or type of data indicated to be shared at block 202 with a listof individuals who may be associated with the NDT system 10. The list ofindividuals may include one or more individuals or groups of individualsthat may have relevant expertise in one or more areas of non-destructivetesting procedures, techniques, results, or the like. Moreover, the listof individuals may also chronicle each individual's experience andknowledge with various types of equipment. Entities may also be listed,such as third party entities (e.g., maintenance service providers,manufacturers), regulatory entities (e.g., Federal AviationAdministration [FAA], Environmental Protection Agency [EPA], Departmentof Transportation [DOT]), federal and state entities, and so on. Thelist of individuals may be received separately from a server via thecloud 24 based on a database that may include a mapping of the data, thedata type, the application, the application type, and the like and listof individuals.

In one embodiment, the application may associate the data received atblock 202 with a problem or issue that corresponds to the equipmentassociated with the data. For example, if the data received at block 202is related to a crack within the airframe of an aircraft 104, theapplication may associate the data with a problem related to thestructural integrity of the airframe or the like. Here, the applicationmay determine that the problem may be associated or related to a groupof individuals and/or entities. As such, the application may send thedata to the group of individuals and/or entities who may be able tobetter assess the problem and assist the NDT operator in solving theproblem.

At block 224, the application may identify individuals for each piece ofdata based on the cross-reference results of block 222. That is, foreach piece of data, the application may identify one or more individualsor entities that may have relevant expertise with regard to theindividual piece of data. Alternatively, for each piece of data, theapplication may identify one or more individuals or entities that mayhave relevant expertise with regard to tagged or identified problems(e.g., defects or defect types).

After identifying the individuals, at block 226, the application maypresent a list of individuals related to a selected piece of data ortype of data on a display. As such, the NDT operator may have theopportunity to view and select one or more individuals to which he maysend the selected data. In certain embodiments, the list of individualsmay be ranked according to the individual's relevant expertise withregard to the selected data. Additionally or alternatively, the list ofindividuals may include details regarding each individual's expertiseand various other characteristics regarding the individual. For example,each individual's entry may include a biography or resume detailinghis/her expertise, which may include number of years in the relevantindustry, equipment familiarity levels, association with pre-designatedgroup of individuals for a particular technology, and the like. Entityentries may include contact personnel, areas of expertise, cost data(e.g., service cost data, manufacturing cost data), and so on. In oneembodiment, each individual's and/or entity's entry may also include apreferred method for communication (e.g., e-mail, text message) anddetails (e.g., e-mail address, telephone number, contact information)regarding the preferred method for communication for each respectiveindividual and/or entity.

In another embodiment, the list of individuals or entities may beorganized based on an organizational structure. For example, a seniorinspector may be presented higher on the list as compared to a newinspector. The list of individuals or entities may also be organizedbased on original equipment manufacturers (OEMs) of the asset beinginspected. As such, the OEMs may receive information related to problemsor inspection results that may be associated with their manufacturedparts. Moreover, the list of individuals or entities may be organizedbased on a creator of an application being executed by the mobile device22, the NDT inspection device 12, or the like. That is, the creator ofthe application being used in the mobile device 22 may wish to receivecertain indications related to the shared data or the shared data,itself.

At block 228, the application may receive an indication or input thatmay designate one or more individuals or entities in the list ofindividuals or entities as recipients. That is, the NDT operator 26, 28,30, 98, 100, and/or 102 may provide input to the application thatindicates which individuals and entities should be recipients to receivethe selected data. After receiving the selection of individuals and/orentities, the application may proceed to block 210 of FIG. 7 and sendthe selected data to the selected individuals. Prior to sending thedata, the application may apply a report template or the like to theselected data such that the selected data may be presented in a morereadable or user-friendly manner. Moreover, upon receiving the shareddata, the recipient may pass comments and flag the data as rejected oraccepted and the data may then be returned to the inspector performingthe inspection, thereby reducing workflow time.

In certain embodiments, the NDT operator 26, 28, 30, 98, 100, and/or 102may observe or acquire data related to the NDT system 10 that may not bepreviously designated as data to be shared. As such, the NDT operator26, 28, 30, 98, 100, and/or 102 may wish to designate data to be sharedin real time soon after the data has been acquired or stored in aninspection report or the like. Keeping this in mind, FIG. 9 depicts aprocess 240 for sharing data related to the NDT system in real time ornear real time. Although the process 240 depicts a particular order inwhich the process 240 may be performed, it should be noted that theprocess 240 may also be performed in a different order. In certainembodiments, the process 240 or portions of the process 240 may beincluded in non-transitory computer-readable media stored in memory,such as the memory 15, 19, 23, 25, 93, 97, 101 and executable by one ormore processors, such as the processors 17, 21, 25, 95, 99, 103 and thecloud 24.

At block 242, the application may receive data related to equipment inthe NDT system 10. For instance, the application may receive results ofan eddy current test on the aircraft 104 frame that indicates that acrack may exist within the airframe. If the data that corresponds to theresults of the eddy current test was not previously designated as datathat will be shared, the application may provide an option to the NDToperator 26, 28, 30, 98, 100, and/or 102 to designate the data to beshared, for example in real-time or near real-time.

As such, at block 244, the application may receive an input indicatingthat the data received at block 242 is to be shared with certain NDTpersonnel. In one embodiment, the application may receive an input at anicon or image depicted on a graphical user interface (GUI) via an inputdevice (e.g., pointing device, keyboard) on the mobile device 22 suchthat the input may designate the data to be shared.

At block 246, the application may receive one or more recipientsdesignated to receive the data associated with the input described abovewith regard to block 244. After receiving the input at block 244, theapplication may present a list of potential recipients on a display. Inaddition to receiving the recipients, the application may receive asharing method as described above with reference to block 204 of FIG. 7.In certain embodiments, the application may present a list of potentialrecipients using a similar process described above with reference toblock 206 of FIG. 7.

After receiving the recipients, at block 248, the application may sendthe data associated with the input of block 244 to the recipientsspecified at block 246. In one embodiment, the application may send thedata as soon as the recipients have been received at block 246. However,in some embodiments, the application may also send the data using aburst transmission. That is, the application may wait to send the datawhen an connectivity signal (e.g., Internet) becomes available. As aresult, the process 240 provides a way to designate data to be sharedwithout pre-designating the data as being shared.

In certain embodiments, after receiving the recipients associated withthe data to be shared, at block 250, the application may receivecomments regarding the data to be shared. For instance, if the receiveddata of block 242 is a screen view of a display (e.g., display 135), theapplication may receive drawings or text or any other data (e.g., datacommunicated via conduit 162) on the screen view from the NDT operator26, 28, 30, 98, 100, and/or 102 to indicate his comments, questions, orconcerns with the data depicted in the screen view (e.g., annotatedoverlays 168). In this manner, the recipient may better understand thecontext of the data and provide advice to the NDT operator 26, 28, 30,98, 100, and/or 102 accordingly. After receiving the comments, theapplication may, at block 248, send the data with the correspondingcomments to the recipient received at block 246.

Keeping the foregoing in mind, the application may also employ a process260 for automatically sharing data acquired from the NDT system 10, asshown in FIG. 10. Referring now to FIG. 10, at block 262, theapplication may receive one or more ranges of data field values for oneor more data fields in the application. For instance, the rage of datafield values may correspond to a range of expected values for thecorresponding data field. The range of expected values may be determinebased on empirical or historical data related to the data field or basedon simulated results for the corresponding data field.

At block 264, the application may receive an input data field value fora respective data field. That is, the NDT operator 26, 28, 30, 98, 100,and/or 102 may perform a test or inspection on a piece of equipment inthe NDT system 10 and enter a reading or measurement in the respectivedata field.

At block 266, the application may determine whether the input data fieldvalue is within a respective range of data field values received atblock 262. If the input data field value is within the respective rangeof data field values, the application may return to block 264 andcontinue receiving input data field values.

If, however, the input data field value is not within the respectiverange of data field values, the application may proceed to block 268. Atblock 268, the application may send the input data field value to one ormore recipients who may be designated as individuals or associated withthe input data field value as described above. In certain embodiments,in addition to the input data field value, the application may sendinformation with regard to the context of the input data field value.For example, the application may send information related to a type ofreport in which the input data field value may exist, an expected rangeof values for the input data field value, date and time informationrelated to when the input data field value was received, and any otherinformation that may provide context for the input data field value suchthat the recipient may properly analyze the input data field value.

In certain embodiments, the input data field value received at block 264may not correspond to a data field that has a range of data field valuesassociated therewith. In this case, the NDT operator 26, 28, 30, 98,100, and/or 102 may specify to the application whether the applicationmay automatically send the input data field value or may not send theinput data field value.

In addition to providing techniques for sharing NDT data, in certainembodiments, the NDT system 10 may provide a computing environment suchthat the NDT operators may collaborate with each other. For example,FIG. 11 depicts a block diagram of a collaboration system 270 that mayprovide a computing environment for NDT operators, experts on NDTinspection devices 12, experts on assets being inspected, and the liketo collaborate with each other with regard to various aspects of the NDTsystem 10. To create this collaborative computing environment, thecollaboration system 270 may include the mobile device 22, a database272, and a client-computing device 274. The client-computing device 274may include for example, a tablet, a cell phone (e.g., smart phone), anotebook, a laptop, a desktop, or any other computing device. In oneembodiment, the mobile device 22, the database 272, and theclient-computing device 274 may directly communicate or exchangeinformation with each other or communicate with each other via the cloud24.

Generally, an NDT inspector 276 (e.g., operator 26, 28, 30, 48, 50, 52)may use the mobile device 22 to perform various types of analysis andmonitoring operations on equipment in the NDT system 10. As such, theNDT inspector 276 may enter data that corresponds to the equipment(e.g., devices 12, 14, 16, 22, 42, 44, 46) in the NDT system 10 into anapplication via the mobile device 22. In certain embodiments, theapplication may analyze or record the data that corresponds to theequipment in the NDT system 10.

While the NDT inspector 276 collects data, the NDT inspector 276 mayenter data or encounter a situation in which he may want to collaboratewith a remote NDT inspector 278. In this case, the NDT inspector 276 mayuse the NDT collaboration system 270 to initiate a field request forsupport from the NDT inspector 278. That is, the NDT inspector 276 mayinitiate a collaboration session with the NDT inspector 278 via thecloud 24. For example, in one embodiment, the NDT inspector 278 may usethe client-computing device 274 to broadcast a status such that eachinspector connected to the NDT collaboration system 270 may be aware ofthe status. The status may indicate the availability, expertise, orother relevant information with regard to the NDT inspector 278. Incertain embodiments, the NDT collaboration system 270 may storeinformation related to the NDT inspector 278 such as a profile thatindicates his experience, technical specialties, certifications, and thelike.

When initiating the field request for support, the NDT inspector 276 maysearch through a list of experts or NDT inspectors 278, who may beindicated as being available via the NDT collaboration system 270. Oncethe NDT inspector 276 selects which NDT inspector 278 they may wish toseek assistance from, the NDT inspector 276 may send a request to therespective NDT inspector via a notification message that may be includeinformation or an interface from which a collaboration session may beinitiated. In certain embodiments, the notification message may be sentto the NDT inspector 278 via e-mail, text message, automated call, orthe like. The notification message may include information suitable forinitiating a collaboration session, such as a URL link, a whiteboardingsession link, and the like, suitable for real time or near real timecollaboration.

After the NDT inspector 276 initiates the collaboration session, the NDTcollaboration system 270 may share the data depicted on the mobiledevice 22 with the remote NDT inspector 278 via the client-sidecomputing device 274 in real time. During this real-time collaboration,the mobile device 22 may be controlled by the NDT inspector 276 via themobile device 22 or by the NDT inspector 278 via the client-computingdevice 274. In one embodiment, the NDT inspector 276 may pass control ofthe screen depicted on the mobile device 22 to the NDT inspector 278 forremote control of the mobile device 22 or the NDT inspection devicebeing controlled by the mobile device 22. When the NDT inspector 278 hasremote control of an NDT inspection device, certain features on the NDTinspection device may be disabled for safety reasons. That is, themobile device 22 may not allow the NDT inspector 278 to remotely controlsome features of the NDT inspection devices, which may place the NDTinspector 276 in an undesired situation. As such, in these cases, themobile device 22 may disable the respective features of the NDTinspection device. For example, the mobile device 22 may disable thefunctionality of an x-ray inspection device or any other NDT inspectiondevice that may initiate physical movements to enhance the safety of theNDT inspector 276.

In certain embodiments, the NDT inspector 276 may enable the mobiledevice 22 to be shared in real time by providing an input to theapplication being executed or running on the mobile device 22. As such,if the input is engaged by the NDT inspector 276, the application maysend data related to the images and controls displayed on the mobiledevice 22 to the client-computing device 274 directly using a wired orwireless interface or indirectly via the cloud 24. Moreover, the NDTcollaboration system 270 may also share the video streams, audiostreams, chat streams, data streams, screen images, and the likeavailable on the mobile device 22 and the client-side computing device274 to add more context to the screen sharing. Data streams may includenumerical data values or other external data such as temperature orhumidity data that may be detected from the ambient air using sensorsdisposed on the mobile device 22, the NDT inspection device 12, or thelike. In one embodiment, the data streams may be received by the mobiledevice 22, the NDT inspection device 12, or the like by interacting orvia communicating with the asset being inspected. In any case, theadditional sharing of video streams, audio streams, data streams, chatstreams, screen images, and the like may help provide more context tothe real-time data sharing session for both the NDT inspector 276 andthe NDT inspector 278.

Additionally, the NDT collaboration system 270 may enable the NDTinspector to access and use NDT measurement and analysis tools runningon the mobile device 22 to diagnose and/or analyze the NDT data. Thatis, during a collaboration session between the NDT inspector 276 and theNDT inspector 278, the NDT inspector 278 may use NDT measurement toolson the mobile device 272 to diagnose or analyze inspection results orNDT data received by the mobile device 22. For instance, the NDTinspector 278 may use various measurement tools, image processing tools,signal-processing tools, and the like to further analyze the NDT data.

In certain embodiments, the measurement and analysis tools may includecollaboration tools such as virtual whiteboarding tools. The virtualwhiteboarding tools may enable either the NDT inspector 276 or the NDTinspector 278 to superimpose writings or drawings onto images thatdepict the shared data. For instance, the virtual whiteboarding toolsmay enable the NDT inspector 276 or the NDT inspector 278 to write ontothe shared data with a virtual pen to draw circles, arrows, or the like.Moreover, the virtual whiteboarding tools may also enable the NDTinspector 276 or the NDT inspector 278 to add text annotations onto theshared data. As a result, the NDT inspector 276 and the NDT inspector278 may better collaborate, troubleshoot, discuss, and analyze with eachother using the virtual whiteboarding tools.

In one embodiment, the NDT collaboration system 270 may provide aconnection to the database 272, which may include a knowledge basesystem that may include contextual information related to the NDT data,analysis of the NDT data, or the like. The knowledge base system mayinclude a historical archive of inspection results and reports relatedto NDT devices, documents (drawings, videos, specifications etc.)related to NDT devices, documents related to the inspection proceduretype (e.g., UT TOFT Weld, ET-Surface etc.) and any other relateddocuments. As such, the knowledge base system may make all the relevantdocuments related to the inspection that is being carried out both forthe NDT inspector 276 and the NDT inspector 278. In one embodiment, theknowledge base system may also provide other analytical informationbased on the historical inspection results. For example, the knowledgebase system may indicate how a crack on a particular blade on theaircraft system 54 may have grown over time.

In certain embodiment, the database 272 may also store a recording ofthe whole session of collaboration between the NDT inspector 276 and theNDT inspector 278. The recording of such a session may be manuallyinitiated by the NDT inspector 276 or the NDT inspector 278 or may beconfigured for automatic recording. The recording may be archived forfuture reference or may be used for training new NDT inspectors or forhistorical references such as previously completed audits.

Keeping the foregoing in mind, FIG. 12 illustrates a method 280 forsharing display data and control of the mobile device 22, for example,via the NDT collaboration system 270. In one embodiment, an applicationin the mobile device 22 may be used to perform the process describedherein. At block 282, the application may receive a request for onlinesupport. As mentioned above, the application may receive the request viaan input interface displayed on the screen of the mobile device 22. Insome embodiments, the request may include the type of equipment underinspection, the type of issues currently found (e.g., cracks,corrosion), the type of NDT inspection device(s) 12 in use, the leveland expertise of the inspector(s) 276, the owner/lessee of the equipmentundergoing inspection, and the like.

The application may, at block 284, connect to the collaboration system270 via a wired or wireless communication, as described above. At block286, the application may receive a list of individuals such as expertsor entities that may be available to support the NDT inspector 276. Incertain embodiments, the application may receive the list of individualswithout connecting to the collaboration system 270. As such, theapplication may receive the list of individuals based on a list ofcontacts that may be stored locally in the device executing theapplication.

The list of individuals may include one or more individuals or groups ofindividuals that may have relevant expertise in one or more areas of NDTprocedures, techniques, results, or the like associated with theapplication currently being executed by the mobile device 22. In certainembodiments, the list of individuals may be organized based on a levelof expertise in the respective application, NDT inspection process, NDTdevice, or the like. As mentioned above, the NDT inspectors 278 maybroadcast their status (e.g., availability) and expertise level over thecollaboration network 270.

At block 288, the application may receive a selection of one or moreindividuals or entities from the list received at block 286. After theselection has been received, at block 290, the application may send asession initiation or notification message to the selected individuals.Accordingly, one or more experts or expert entities may participate toaid in inspection 154 and/or analysis 156. As such, the respective NDTinspector 278 may receive a notification message that may includeinformation or an interface (e.g., link) from which a collaborationsession may be initiated. In certain embodiments, the notificationmessage may be sent to the NDT inspector 278 via e-mail, text message,automated call, or the like.

By providing the NDT collaboration system 270, the NDT inspector 276 mayperform his inspection tasks or data analysis with the assistance of oneor more of the NDT inspector 278 in real time. As such, the amount oftime in which the NDT inspector 276 may take to perform his tasks maydecrease through the real-time collaboration and support from the NDTinspector(s) 278, who may be an expert. It is to be noted that, in someexamples, the NDT inspector 278 may include software or hardware systemssuch as expert systems, expert logic reasoning systems, and the like,that may “answer” questions based on artificial intelligence (AI)techniques and knowledge repositories. Moreover, the NDT collaborationsystem 270 may bridge the knowledge gap of the NDT inspector 276 and theNDT inspector 278 through real-time sharing of analysis tools andrecommendations provided by the NDT inspector 278. Further, by providingaccess to information related with the data being analyzed or the likeusing the knowledge base system, the analysis performed by the NDTinspector 276 may be more accurate. Additionally, by storing recordedcollaboration sessions, the collaboration system 270 may provideimproved training to the new inspectors based on historical scenarios.

In order to improve the safety operations of the NDT devices, it may bebeneficial to control the operations of the certain NDT devices whilethe mobile device 22 is operating during a collaboration session. Thatis, given the hazardous nature of certain NDT devices, such as an x-rayinspection device, care should be taken to avoid operating the NDTdevice remotely without regard to the presence and location of thefield-operating NDT inspector 276. Accordingly, FIG. 13 illustrates amethod 300 that may be used to safely operate certain NDT devices whileoperating in a collaboration session.

At block 302, the application on the mobile device 22, which may belocated within a close proximity to the NDT device it may control, mayenter a collaboration session with a remote user such as the NDTinspector 278 via the cloud 24 and the client-computing device 274.While operating in the collaboration session, the application may enablereal-time sharing of the application being executed on the mobile device22 between the NDT inspector 276 and the NDT inspector 278. As such, theapplication may share data depicted on the screen of the mobile device22, control of the mobile device 22 or the respective NDT inspectiondevice, and the like.

At block 304, the application may determine whether the control of themobile device 22 or the respective NDT inspection device operated viathe mobile device 22 may be shared with a remote user such as the NDTinspector 278. If the control is indeed shared with a remote user, theapplication may proceed to block 306.

At block 306, the application may automatically disable certainoperational functions of the NDT inspection device or certain optionsfor control of the NDT inspection device via the mobile device 22. Incertain embodiments, control may be retrieved by the NDT inspector 276at any time to disable certain operational functions of the NDTinspection device or certain options for control of the NDT inspectiondevice to ensure that the NDT inspection device is being operatedsafely. Referring back to the x-ray inspection device example, at block306, the application may disable the emission of x-rays from the x-rayinspection device to ensure that x-rays of unsuspecting individuals maynot be performed remotely. Although certain operational functions of theNDT inspection device may be disabled, the NDT inspector 278 may stillbe able to use the measurement and analysis tools on the mobile device22 to further analyze, troubleshoot, or assist the NDT inspector 276.

In certain embodiments, the application may proceed to block 306 after adetermination has been made that the NDT inspection device beingcontrolled by the application corresponds to a hazardous or potentiallyhazardous NDT inspection device. For example, if the NDT inspectiondevice is a PTZ camera, the application may not proceed to block 306 todisable certain feature of the PTZ camera because the remote operationof the PTZ camera may not create a hazardous environment.

Referring back to block 304, if the application determines that thecontrol is not shared with a remote user, the application may return toblock 302 and remain in the collaboration session. As such, the NDTinspector 276 may continue to share the data depicted on the screen ofthe mobile device 22.

In addition to the features described above, the NDT collaborationsystem 220 may also enable data being depicted on the NDT device 12 orbeing generated on the mobile device 22 to be streamed onto theclient-computing device 274. As such, the NDT collaboration system 270may allow NDT inspector 276 to stream their NDT inspection live to theNDT inspector 278 while running an application, menu-driven interface,or the like. In certain embodiments, using location awarenesstechnology, the NDT collaboration system 270 may also provide the NDTinspector 278 with applicable and relevant information stored on thedatabase 272 related to a specific asset or component currently beingdisplayed or inspected. For instance, relevant information may includedata fields that correspond to an inspection report for an inspectionprocess currently being performed. Additionally or alternatively, therelevant information may include historical NDT data related to theassets, NDT data for other like assets, measurement informationassociated with the respective NDT device 12 or the assets, measurementlimits associated with the respective NDT device 12 or the assets,service bulletins associated with the respective NDT device 12 or theassets, technical manuals associated with the respective NDT device 12or the assets, updated technical specifications associated with therespective NDT device 12 or the assets, original equipment manufacturer(OEM) recommendations associated with the respective NDT device 12 orthe assets, industry standard operating procedures (SOP), maintenanceshop manuals, and the like. As such, the mobile device 22 may streamlive its current inspection data including information with regards tothe asset it is inspecting and the respective location within thatasset. Moreover, using this information, the NDT collaboration system270 may automatically retrieve information to provide the NDT inspector276 and the NDT inspector 278. Accordingly, the relevant information maybe made available to both the NDT inspector 276 and the NDT inspector278 to better enable either inspector to analyze the data and inspectionprocess.

Keeping the foregoing in mind, FIG. 14 illustrates a process 310 forproviding location aware data while retrieving data from the NDTinspection devices 12. Like the processes described above, the process310 or portions of the process 310 may be included in non-transitorycomputer-readable media stored in memory, such as the memory 15, 19, 23,25, 93, 97, 101 and executable by one or more processors, such as theprocessors 17, 21, 25, 95, 99, 103, the computing system 29, and thecloud 24.

In one embodiment, an application containing computer instructionsexecutable by the mobile device 22, the NDT inspection devices 12,computing system 29, and/or the cloud 24 may be used to collect datathat may be related to the inspection of a piece of equipment (e.g.,devices 12, 14, 16, 22, 42, 44, 46) within the NDT system 10 or may beused to generate reports 159 related to the NDT system 10. Although theprocess 310 depicts a particular order in which the process 310 may beperformed, it should be noted that the process 310 may also be performedin a different order.

Referring now to FIG. 14, at block 312, the application may enter into amode in which it shares data with one or more recipients in real time asdescribed above. While sharing the data, at block 314, the applicationmay determine location information associated with the shared data.Location information may include a physical location within equipment(e.g., turbomachinery 18) being inspected by the respective NDTinspection device 12. For instance, in the case of equipment such as theturbomachinery 18, the location information may indicate whether thedata displayed on the mobile device 22 or the data retrieved by themobile device 22 corresponds to a combustion chamber of theturbomachinery 18, a compressor of the turbomachinery 18, or the like.

In certain embodiments, the application may determine the locationinformation based on the data being retrieved by the mobile device 22from the NDT inspection device 12 and other information related to theinspection process such as the type of equipment being inspected, anamount of time in which the inspection has been in progress, empiricaldata related to the inspection process employed by the NDT inspector276, and the like. For example, the application may determine that thedata being entered into the mobile device 22 may be associated with thecombustion chamber of the turbomachinery 18. As such, the applicationmay determine that the mobile device 22 may located in the combustionchamber of the turbomachinery 18.

In another example, the application may determine an amount of time thathas passed since the NDT inspector 276 started his inspection processand compare that time to the inspector's history or empirical datarelated to the inspector's previous inspections for similar equipment.Based on that comparison, the application may estimate or approximatewhich portion of the inspection process that the inspector may currentlybe and may determine a location within the respective equipment that maycorrespond to the portion of the inspection process that the inspectormay currently be.

Further, determining a location [from empirical data?] may includemonitoring NDT inspector's 276 position in a workflow, a Menu DrivenInspection (MDI) process, or an application or feature of NDT inspectiondevice 12 or mobile device 22 that guides NDT inspector 276, i.e., aguided inspection application. Additionally, NDT inspector 276 or NDTinspector 278 may identify, tag, or otherwise enter the locationinformation.

The mobile device 22 may also include additional circuitry orapplications that may be used to determine the location information. Forinstance, the mobile device 22 may use indoor global positioning system(GPS) technology, image recognition technology, radio frequencyidentification (RFID) technology, barcode technology, optical characterrecognition (OCR) technology, triangulation (e.g., WiFi triangulation,radio triangulation) and the like to determine the location within theequipment being inspected. By way of example, if the shared data ofblock 312 includes a live video feed of an inspection being performedwithin an asset, the application may use image recognition software toidentify certain parts of the equipment and determine a location withinthe equipment based on the identified parts. In the same manner, theapplication may receive inputs from the indoor GPS technology, RFIDtechnology, barcode technology, OCR technology, and the like and comparethe input data to a legend or key to determine the location within theequipment being inspected. The legend or key may be stored, in certainembodiments, in the database 222 or the like.

Keeping this in mind, at block 316, the application may determine oridentify an asset or assets being inspected or that corresponds to thedata being shared at block 262. The asset may correspond to a componentwithin the equipment being inspected. For example, the assets of theturbomachinery 18 may include a combustion chamber, a compressor, or thelike. In one embodiment, the application may determine or identify theasset based on the location information determined at block 314.Additionally or alternatively, the application may use the imagerecognition technology, the indoor GPS technology, RFID technology,barcode technology, OCR technology, triangulation, and the like toidentify the asset being inspected. That is, the application may receiveinformation from the image recognition technology, the indoor GPStechnology, RFID technology, barcode technology, OCR technology,triangulation, and the like that may indicate the asset or type of assetrelated to the data received at block 312.

After identifying the assets that correspond to the data shared at block312, at block 318, the application may determine or identify informationrelated to the respective asset. That is, the application may identifyrelevant asset information based on the location within the asset thatcorresponds to the data shared at block 312. The relevant assetinformation may include inspection reports or any data entry tool thatmay be part of the inspection process or reporting that the NDTinspector 276 may perform. As such, as the NDT inspector 276 approachesa particular asset, the application may display a data field in aninspection report related to the particular asset. In this way, the NDTinspector 276 may more efficiently enter data by, for example, reducedinteraction with the application.

In certain embodiments, the NDT inspector 276 and the NDT inspector 278may also retrieve additional information related to the identifiedasset. As such, the relevant asset information may also include previousinspection data for the identified asset, inspection data for other likeassets, measurement information for the identified asset, measurementlimits for the identified asset, service bulletins or updates for theidentified asset, technical manuals or updated technical manuals for theidentified asset, original equipment manufacturer (OEM) recommendationsfor the identified asset, and the like.

The relevant information may be stored locally on the mobile device 22,the client-side computing device 274, or the like. Alternatively oradditionally, the relevant information may be stored in the knowledgebase system in the database 272. As such, the application may retrievethe relevant information from the database 272 via the cloud 24. In oneembodiment, the application may display a tag or a brief textdescription of the relevant information related to the shared data onthe screen of the mobile device 22. Here, the NDT inspector 276 or theNDT inspector 278 may retrieve the relevant information upon interactingwith the tag or text description.

At block 320, the application may display the relevant information, or aprompt therefor, on the screen of the mobile device 22 or on the databeing shared at block 312. For example, if the data being sharedincludes a video feed, the application may super impose a link orgraphical user interface (GUI) icon or graphic, which may connect to therelevant information, or the information may be displayed in anotherwindow or screen of the GUI.

In other embodiments, the NDT collaboration system 270 may be used toperform various types of data analysis techniques. That is, the cloud 24may include a computing network with a number of processors that mayanalyze data using various types of algorithms and the like. As such,the cloud 24 may be used to perform various types of analysis that maybe computationally intensive or may not be performed efficiently on themobile device 22 or the client-side computing device 274. The dataanalysis may be performed on the data acquired by the NDT inspectiondevices 12 and may include applying various types of algorithms (e.g.,filters) to the data, generating visualizations that depict the data,and the like. In certain embodiments, the data analysis may includeapplying predictive analytic algorithms to the data to determine theuseful life of an asset associated with the data or the like.

By employing servers and/or services in the cloud 24 to analyze data,the NDT inspector 276 and/or the NDT inspector 278 may analyze datacaptured by NDT inspection devices 12 using the processing capabilitiesof the cloud 24, as opposed to the processing capabilities of a localmachine such as the mobile device 22 or the client-side computing device274. In this manner, the NDT inspector 276 may acquire data via themobile device 22 and the NDT inspection device 12 while performing aninspection operation in the NDT system 10. After acquiring the data, themobile device 22 may automatically send the data to the cloud 24, whichmay be executing one or more customized algorithms on the data. Afterexecuting the algorithms, the cloud 24 may return the results or theanalyzed data back to the mobile device 22 using the collaborationsystem 220.

As the cloud 24 receives the data, the cloud 24 may identify and savemetadata regarding the data in a storage or memory within the cloud 24,the database 272, or the like. The metadata may include information thatcorresponds to the asset being inspected, the methods used to inspectthat asset, measurements received from that asset, componentidentification information pertaining to that asset, and the like. Incertain embodiments, the cloud 24 may categorize the metadata and storethe metadata with respect to its categories. In other embodiments, thecloud 24 may analyze the data and/or metadata with respect to certainvariables. For example, the cloud 24 may compare the data acquired bythe NDT inspection device 12 to data previously acquired by therespective NDT inspection device 12, data acquired by a fleet of the NDTinspection devices 12, data acquired by like assets, known values (e.g.,measurement gates), and the like.

Keeping the foregoing in mind, FIG. 15 depicts a flowchart of a process330 that may be employed by the mobile device 22, the client-sidecomputing device 274, the NDT inspection device 12, or the like toanalyze NDT data using the collaboration system 270. In particular, theprocess 330 is related to analyzing data acquired by the NDT inspectiondevice 12 using the cloud 24 of the NDT collaboration system 270.

In one embodiment, an application containing computer instructionsexecutable by the mobile device 22, the client-side computing device274, the NDT inspection devices 12, computing system 29, and/or thecloud 24 may be used to perform the process 330. Although the process330 depicts a particular order in which the process 330 may beperformed, it should be noted that the process 330 may also be performedin a different order.

Referring now to FIG. 15, at block 332, the application may receive rawdata that may have been acquired by the NDT inspection device 12. Theraw data may be identified or designated by the NDT inspector 276 or theNDT inspector 278 as data that should be analyzed using one or morealgorithms. As such, in one embodiment, the application may send the rawdata to the cloud 24 for analysis. That is, the cloud 24 may employ itsprocessors to analyze the data, as opposed to the data being analyzed onthe mobile device 22 or the client-side computing device 274, which maynot have the same processing power as the cloud 24. For example, thecloud 24 may include one or more virtual machines (VMs), servers,storage, load balancers, network caching, and the like suitable forexecuting cloud computing analytics.

In certain embodiments, as the raw data is received by the NDTinspection device 12, the NDT inspector 276 or the NDT inspector 278 mayindicate to the application one or more algorithms in which to processthe raw data using the cloud 24. By analyzing the raw data using theprocessor(s) in the cloud, the NDT inspector 276 or the NDT inspector278 may analyze the raw data more efficiently. That is, since thecomputing network of the cloud 24 may include scalable computing systemsor processors and may, as a result, generally include more processingpower than the mobile device 22 or the client-side computing device 274.In this way, the NDT inspector 276 or the NDT inspector 278 may continuethe inspection process or analyze other data while the cloud 24processes or analyzes data that may use more processing power thanavailable on the mobile device 22 or the client-side computing device274.

Keeping the process 330 in mind, FIG. 16 illustrates a process 340 thatthe cloud 24 may employ when analyzing the raw data acquired by themobile device 22 via the NDT inspection device 12. Like the mobiledevice 22, the cloud 24 may include an application (e.g., cloudapplication) that may include computer instructions executable by thecloud 24 to analyze the data acquired by the NDT inspection device 12.As such, at block 342, the cloud application may receive the raw datasent by the mobile device 22 (block 334). In addition to the raw data,the cloud application may receive an indication of one or morealgorithms in which to analyze the received data. In certainembodiments, the algorithms may be customized algorithms that may beuploaded to the cloud 24 and designed by a developer of the applicationfor the mobile device 22, a developer of the cloud application, athird-party developer, or the like.

At block 344, the cloud application may analyze the data received atblock 342 using its respective processor(s). As such, the cloudapplication may analyze the data using the algorithms specified by theNDT inspector 276 or the NDT inspector 276 as described above. In oneembodiment, the data analysis may be performed by the NDT inspector 276or an expert connected to the cloud 24 using the data analysis toolsavailable to the cloud 24. The data analysis tools may analyze the datafor measurements associated with the asset being inspected, assistedand/or automatic defect recognition for the asset being inspected,disposition information on an asset and/or component being inspected,asset and/or component history, and the like. In one embodiment, theanalyzed data may include one or more instructions for the NDT inspector276 to acquire additional data, to revise the manner in which the datais acquired, or the like based on the results of the analysis.

By way of example, if the data received at block 342 is associated withultrasound waveforms or data acquired while inspecting a weld, theultrasound data may be received by the cloud 24 at block 342 andanalyzed by an expert at block 344. As such, the expert may applyvarious filters on images that correspond to the ultrasound data, whichmay accentuate defects in the weld or remove various artifacts or noisefrom the ultrasound data, thus improving inspection analysis. In oneembodiment, the cloud application may analyze the metadata received withthe ultrasound data associated with the weld to determine possible typesof defects (e.g., lack of penetration or fusion, existence of crack,etc.) that may present in the weld. The analysis performed by the cloudapplication may also include generating a report that may summarize thefindings of the analysis, provide a summary of the data and the metadataacquired by the NDT inspection devices 12, provide a list of outcomes orrecommendations associated with the findings, the data, or the metadata,and the like. For example, the report may list each defect that may bepresent with the weld. In each entry, the report may indicate additionalinformation regarding the respective defect such as a size, location,and type of defect.

In another example, if the data received at block 342 is associated witheddy current inspection data, the cloud 24 may be used to analyze theeddy current inspection data at block 344. Eddy current data analysismay be performed by various sophisticated analysis algorithms useful inderiving observations of eddy currents traveling through ferrous ornon-ferrous material, which may be executed more efficiently using theprocessing power of the cloud 24. In certain embodiments, variousanalysis algorithms may be performed multiple times for multipleiterations to obtain more accurate results. Again, by performing thesetypes of calculations on the cloud 24, as opposed to the mobile device22 or the client-side computing device 274, the NDT inspector 276 and/orthe NDT inspector 278 may obtain more accurate analysis data moreefficiently.

In yet another example, the cloud 24 may also be used to analyzeradiography data. Here, the NDT inspector 274 or an expert may analyzethe radiography data using the cloud 24. For instance, the cloud 24 maybe used to apply a Flash Filter™ or other similar analysis tools to theradiography data.

In certain embodiments, the data received at block 342 may be receivedcontinuously such that the data is streaming into the cloud 24. As such,at block 344, the cloud 24 may continuously analyze the data as it isstreamed into or received by the cloud 24.

After the raw data has been analyzed, at block 346, the cloudapplication may send the analyzed data back to the respective mobiledevice 22 or the respective client-side computing device 274 that sentthe data received at block 342. As such, the NDT inspector 276 or theNDT inspector 278 may receive the results of the analysis and continuethe inspection or data gathering process based on the results.

In addition to analyzing the data using the cloud 24, the NDTcollaboration system 270 may be used to organize and/or categorize dataacquired by the NDT inspection devices 12. FIG. 17 depicts a process 350for sending data and/or metadata acquired by the NDT inspection device12 via the mobile device 22 to the cloud 24.

Like the process 330 of FIG. 17, an application containing computerinstructions executable by the mobile device 22, the client-sidecomputing device 274, the NDT inspection devices 12, computing system29, and/or the cloud 24 may be used to perform the process 350.Moreover, although the process 350 depicts a particular order in whichthe process 350 may be performed, it should be noted that the process350 may also be performed in a different order.

Referring now to FIG. 17, at block 352, the application may receive dataacquired by the NDT inspection device 12. The application may then, atblock 354, identify metadata associated with the data received at block352. The metadata may include information that corresponds to the assetbeing inspected, the methods and/or inspection protocols being used toinspect the asset, measurements associated with the assets, componentidentifications that may be part of the asset, and the like. Afteridentifying the metadata, at block 356, the application may send thedata and/or the identified metadata to the cloud 24, which may analyzeand/or organize the data and/or the metadata as described below withreference to FIG. 18.

Keeping this in mind, FIG. 18 depicts a flowchart of a process 360 thatmay be used by the cloud application to organize data and/or metadatareceived from the mobile device 22 or the like. As such, at block 362,the cloud application may receive data and/or metadata from the mobiledevice 22 or any other device coupled to the cloud 24. The data receivedat block 362 may have been acquired by the NDT inspection device 12 asdescribed above. In the same manner, the metadata may have beenidentified by the application executing in the mobile device 22 asdescribed above with reference to FIG. 17. In one embodiment, the cloudapplication may identify or extract the metadata from the received data.

In any case, at block 364, the cloud application may categorize ororganize the data and/or metadata. For instance, the cloud applicationmay categorize the data and/or metadata based on the asset beinginspected, whether the asset being inspected is part of a fleet ofassets, the inspection process used to inspect the respective asset, andthe like.

The fleet of assets may include a group of assets of a particular type,model, or group that may be in service at various locations. When datais categorized according to its fleet, the cloud application may becapable of performing additional data analysis using the data acquiredfrom similar assets of the same fleet. For example, a first entity mayuse a particular asset for a chemical processing plant while a secondentity may use the same type of asset for a packaging plant. Each assetoperating in different environments may operate under differentconditions. As such, the first entity may be interested in knowing howthe asset may operate under conditions that may be similar to how thepackaging plant uses the asset, while the second entity may beinterested in knowing how the asset may operate under conditions thatmay be similar to how the packaging plant uses the asset. Bycategorizing the data and the metadata associated with the same type ofasset together, the cloud application may build an inventory of datathat may be analyzed to determine more details as to the operations,operational life, capabilities, and the like with regard to theparticular asset.

In one embodiment, the cloud application may alter or modify the dataand/or metadata such that the owner of each asset may be anonymous. Forinstance, the cloud application may remove any information in the dataand/or metadata that may indicate where the asset is installed, who theasset has been purchased by, and the like. In this manner, the assetowners may be inclined to allow the cloud application to categorizetheir respective data as part of its respective fleet without providingsensitive details as to their particular processes or operations.

At block 366, the cloud application may store the categorized dataand/or metadata in a memory. In one embodiment, the categorized dataand/or metadata may be stored in the database 272 or the like. As such,the categorized data and/or metadata may be available to the NDTinspector 276, the NDT inspector 278, an expert, or the like foranalysis. That is, the NDT inspector 276, the NDT inspector 278, theexpert, or the like may analyze data that corresponds to its respectiveasset with respect to data in various categories.

In certain embodiments, at block 368, the cloud application may analyzethe categorized data and/or metadata to determine trends, operationallife, maximum and minimum parameters, and various other types of detailswith regard to each category of data. The cloud application may alsogenerate a report that may summarize the analysis performed by the cloudapplication. After analyzing the categorized data and/or metadata, thecloud application may send the results of the analysis (e.g., report)back to the mobile device 22 or the like. It should be noted that whenthe mobile device 22, the client-side computing device 274, the cloud24, or the like sends data or information within the collaborationsystem 270, the data may be encrypted prior to being sent and decryptedonce received to protect the integrity of the data or information beingsent.

In addition to the above-described processes for analyzing data acquiredby the NDT inspection devices 12, the mobile device 22 or the cloud 24may provide a way in which various review and analysis protocols orworkflows may be implemented for data acquired from different NDTinspection devices 12. That is, an application executed by the mobiledevice 22, the cloud 24, the client-side computing device 224, or thelike may be used to define a workflow for reviewing or analyzing data(NDT data) acquired by the NDT inspection devices 12 based on the typeof NDT data that is being analyzed. In other words, the NDT inspector276 may use a single platform to review and analyze various types of NDTdata, regardless of which type of NDT inspection device 12 was used tocollect the NDT data. That is, the techniques described herein mayprovide a flexible, multimodal approach in performing a comprehensiveanalysis on an asset being inspected, as opposed to being limited to aspecific mode of analysis (e.g., x-ray).

In conventional NDT data analysis systems, however, the available reviewand analysis applications provide only one analysis protocol or workflowfor all types of NDT data (e.g., ultrasound, eddy current, radiography,visual inspection etc.). As such, the workflows, data presentationlayouts, and data analysis tools provided by the conventional NDT dataanalysis systems are fixed and rigid. As a result, users of theconventional NDT analysis systems may be limited in performing variousreview and analysis techniques. Moreover, less experienced users mayfind it difficult to properly review and/or analyze the NDT data usingthe workflow provided by the conventional NDT data analysis system sincethe conventional NDT data analysis system may provide too many optionsfor analysis (e.g., providing x-ray analysis tools when receiving eddycurrent NDT data).

Keeping this in mind, the techniques described herein may enable anapplication executed by the mobile device 22, the cloud 24, theclient-side computing device 224, or the like to provide a particularworkflow for reviewing and analyzing NDT data based on the type of NDTdata being reviewed. The workflow may include displaying the NDT dataaccording to a pre-configured layout, providing a particular set oftools to analyze the respective NDT data, pre-processing the NDT dataaccording to viewer presets or other image pre-processing rules, and thelike. The workflow may also include generating reports based on theanalyzed NDT data, automatically sending inspection results, reports, orthe like. Additionally, the workflow may include retrieving varioustypes of reference material such as reference codes, drawings, anduser-interface elements that may simulate the actual inspection processto provide additional context to the user when reviewing or analyzingthe NDT data.

In certain embodiments, the workflow may be encoded within theapplication and may be retrieved by the application based on a templatebeing used to analyze the NDT data. The template may be prepared with acommon set of semantics such that the same template may be used in anycomputing device such as a desktop-based review station or aweb/cloud-based review station (e.g., mobile device 22, cloud 24, orclient-based computing device 278). Such a template may be associatedwith metadata associated with certain inspection results. For example,the application may retrieve a template to review or analyze the NDTdata based on the metadata associated with the NDT data. In this case,once the application retrieves the appropriate template, the templatemay dictate to the application a workflow in which to review and analyzethe NDT data. As such, the workflow may indicate to the application topresent a particular review and analysis screen with a particularscreen, layout, set of tools, set of presets etc. In one embodiment, theworkflow may execute a particular data analysis application that may beused to analyze the particular NDT data acquired by the NDT inspectiondevices 12.

In other embodiments, the platform or operating system used to performthe NDT data analysis may determine or identify an appropriate workflowfor the NDT data currently being displayed or accessed by the NDTinspector 276, the NDT inspector 278, an expert, or the like. In thiscase, the platform may dynamically change the application being used toanalyze the NDT data, dynamically change the data analysis toolsprovided, or the like based on the NDT data currently being accessed.For example, if the platform is currently providing data analysis toolsthat may be used to analyze eddy current data, the platform maydynamically change the data analysis tools being provided to dataanalysis tools for analyzing x-ray data when the platform receives x-raydata for review or analysis. That is, the platform may recognize thatx-ray information is currently being viewed or accessed, and as aresult, the platform may provide x-ray data analysis tools for the user.

Keeping the foregoing in mind, FIG. 19 depicts an embodiment of aprocess 370 for implementing a workflow for reviewing and/or analyzingNDT data acquired by the NDT inspection devices 12. In one embodiment,an application containing computer instructions executable by the mobiledevice 22, the client-side computing device 274, the NDT inspectiondevices 12, computing system 29, and/or the cloud 24 may be used toperform the process 370. Although the process 370 depicts a particularorder in which the process 370 may be performed, it should be noted thatthe process 370 may also be performed in a different order.

At block 372, the application may receive data (NDT data) acquired bythe NDT inspection devices 12. In certain embodiments, the NDT data maybe received by the cloud 24 such that the analysis of the NDT data maybe performed on the cloud 24. As such, the NDT data analysis workflowsand/or tools may not be limited by the capabilities of a local devicesuch as the mobile device 22 or the client-side computing device 278.

In any case, at block 374, the application may determine an appropriateuser workflow to implement for reviewing and analyzing the received NDTdata. The user workflow may specify a set of processes, methods, or thelike in which the application may implement when the NDT data is beingreviewed or analyzed. Moreover, the user workflow may also define one ormore individuals (e.g., experts) or entities that may have access to theNDT data or may be requested to review and/or analyze the NDT data.Additionally, the workflow may define who may receive a report oranalyzed NDT data after a report has been generated or the NDT data hasbeen analyzed.

In general, the user workflow may define a process in which the user ofthe application may employ when reviewing and analyzing the NDT data.That is, the workflow may define a particular set of NDT data processingsteps to use when analyzing or reviewing the NDT data. For instance,when reviewing radiography data, the corresponding workflow mayautomatically apply certain filters to the images that correspond to theradiography data to remove noise and other undesired artifacts that maybe present in the images. In certain embodiments, the application mayuse the user workflow to ensure that the review/analyzer (e.g., NDTinspector 278) follows the entire user workflow. For instance, theapplication may prohibit the reviewer from performing various types ofanalysis or the like until certain techniques or processes have beenimplemented.

The user workflow may also include applying various pre-processingalgorithms to the NDT data such as applying filters and the like toremove noise from image data. Additionally, the user workflow may definepost-processing steps such as sending the NDT data to other dataprocessing centers, creating reports based on the NDT data or theanalyzed NDT data, sending the reports to various personnel in the NDTsystem 10, and the like. Each of these user workflow processes may beimplemented automatically by the application to help enable the user toreview and/or analyze the NDT data more effectively and efficiently.Moreover, the application may help ensure that the user employs theappropriate user workflow process when reviewing and/or analyzing theNDT data. In this manner, the application may ensure that the NDT datais reviewed and/or analyzed according to a specified procedure.

Referring back to block 374, the appropriate user workflow for the NDTdata may be determined based on a mode in which the application may beexecuted, a type of NDT inspection device 12 used to acquire the NDTdata, the NDT methodology employed to acquire the NDT data, and thelike. The appropriate workflow may also be defined in metadataassociated with the NDT data. That is, the metadata may indicate thetype of NDT data that may be received, the appropriate user workflow toimplement for analyzing the NDT data, or the like. Using the informationprovided by the metadata, the application may then determine anappropriate user workflow for reviewing and/or analyzing the NDT data.

In certain embodiments, the user workflow may be customized based on theNDT data being reviewed or analyzed. That is, different types of NDTdata may use different user workflows when analyzing the respective NDTdata. For instance, eddy current data may differ significantly fromradiography data. As such, the review and/or analysis processing stepsand/or tools used to analyze the respective NDT data may differsignificantly. In this way, the user workflow determined at block 374may correspond to the type of NDT data being analyzed such that theprocess for reviewing and/or analyzing the NDT data may be performedmore efficiently.

After determining the appropriate user workflow, at block 376, theapplication may implement the appropriate workflow as described above.As such, the application may verify that the user perform various stepsin the user workflow with the NDT data before proceeding to other steps.The application may also display messages or instructions that specifyhow the NDT data may be analyzed according to the workflow. In certainembodiments, after implementing the user workflow at block 376, theapplication may repeat the process 370 such that the user workflow maychange dynamically based on the NDT data being reviewed (i.e., receivedat block 372).

By automatically implementing the workflow for the NDT data analysisreview, the application may make the make reviewing and analyzing theNDT data more efficient. That is, the workflow-based application mayhelp improve the inspection workflow process and thus save time for theuser reviewing or analyzing the NDT data. Moreover, the application mayalso ensure that a particular process or certain review rules areperformed by the reviewer by encoding the workflow to prevent thereviewer from proceeding to certain steps in the workflow until othersteps have been completed.

The application may also generate an appropriate layout to display theNDT data and data analysis tools that may be used to analyze the NDTdata. FIG. 20 illustrates a flowchart of a process 380 that may be usedto display the appropriate layout and tools for a user. At block 382,the application may receive NDT data as described above with respect toblock 372. That is, the NDT data may be received by the application suchthat it may be reviewed or analyzed.

After receiving the NDT data, at block 384, the application maydetermine an appropriate layout in which to display the NDT data. Incertain embodiments, the application may determine the appropriatelayout based on a modality (e.g., eddy current, radiography, etc.) thatcorresponds to the application being executed. In another embodiment,the application may determine the layout based on an indication receivedfrom the user via an input device such as a keyboard, keypad, or thelike. In yet another embodiment, the application may determine thelayout based on the asset or component in which the NDT data represents.As such, the application may present the NDT data using a particularlayout or in a particular graphical mode based on the mode in which theapplication is operating, an input received from the user of theapplication, the type of NDT data being analyzed, accessed, ordisplayed, or the like. In certain embodiments, this information may beembedded within metadata associated with the received NDT data.

The layout may, in some cases, be pre-determined by the user of theapplication according to his preferences for reviewing and/or analyzingthe NDT data. Alternatively, the application may determine theparticular layout based on the NDT data and historical references withregard to layouts used to analyze the respective NDT data. The layoutmay include a manner in which the NDT may be organized or presented tothe user. For example, the NDT data may be organized according tospecific assets being inspected, times and/or dates in which inspectionsoccurred, particular jobs associated with an inspection, or the like.

After receiving the NDT data at block 382 or determining the appropriatelayout for the NDT data at block 384, at block 386, the application maydetermine an appropriate data analysis tools that may be used to analyzethe NDT data received at block 382. In one embodiment, the set of dataanalysis tools may be defined in the user workflow described above withreference to FIG. 19. Otherwise, the application may independentlydetermine the set of data analysis tools based on the NDT data beingaccessed, the metadata associated with the NDT data, an indicationreceived from the user of the application, or the like. In any case, theset of data analysis tools may cater to the type of NDT being analyzed.That is, each type of NDT data (e.g., eddy current, radiography,ultrasound, visual) may be associated with a specific set of tools thatmay be used to analyze and/or review the NDT data. For instance, the setof data analysis tools may include various image filters when the NDTdata corresponds to radiography data; however, the set of data analysistools may not include the image filters when the NDT data corresponds toeddy current data since eddy current data may not include any images.

After determining the appropriate layout to display the NDT data and/orthe appropriate set of data analysis tools for the NDT data, at block388, the application may import the layout and/or the set of dataanalysis tools for the user to review and/or analyze the NDT data. Inone embodiment, the set of data analysis tools may be displayed on thescreen of the mobile device 22, the client-side computing device 272, orthe like according to the layout. After importing the layout and/or dataanalysis tools, the application may repeat the process 380 for each timeNDT data is received by the application. As such, the application maydynamically change the layout and/or data analysis tools based on theNDT data currently being accessed or analyzed.

In certain embodiments, a different set of data analysis tools may beimported for different parts of the user workflow. That is, differentparts of the user workflow may include different types of data analysistechniques that may use different types of data analysis tools. Bycontinuously importing the appropriate data analysis tools while theuser analyzes or reviews the NDT data according to the user workflow,the application may enable the user to efficiently analyze the NDT data.Moreover, by providing the appropriate data analysis tools as the useranalyzes the NDT data according to the user workflow, the applicationmay assist less-experienced users (i.e., reviewers) by automaticallyselecting the data analysis tools that may be of use to them. Further,automatically providing the data analysis tools may also helpexperienced users by simplifying the data analysis tools provided in theuser interface of the application or by providing the appropriate dataanalysis tools without any input from the user.

Although the process 370 and the process 380 described above may beperformed by the NDT inspector 276, the NDT inspector 278, or the likeusing the mobile device 22, the client-side computing device 274, or thelike, it should be noted that the process 370 and the process 380 may beused in conjunction with the cloud 24 to enable an individual (e.g., anexpert) to log into the application via the cloud independent of anyinspection procedure. That is, the expert may access NDT data via thecloud 24 using the application, and the application may, in turn, enablethe expert to view and analyze all types (e.g., modalities) of NDT datausing a number of user workflows, layouts, data analysis tools, and thelike. As such, the expert is given an opportunity to receive acomprehensive view into the health or status of an asset or componentthat has been inspected.

Keeping this in mind, FIG. 21 depicts a process 390 that may be used toenable an expert to analyze NDT data via the cloud 24. In oneembodiment, an application containing computer instructions executableby the cloud 24 may be accessed using the mobile device 22, theclient-side computing device 274, and/or the computing system 29 toperform the process 390. Although the process 390 depicts a particularorder in which the process 390 may be performed, it should be noted thatthe process 390 may also be performed in a different order.

As such, at block 392, the application may receive user identificationinformation such as a login name, password, or the like. Based on thereceived user identification information, the application may, at block394, generate a layout and/or data analysis tools for the expert. Thatis, the application may generate a layout or present the NDT dataaccording to a layout that may have been specified as a preference bythe expert. In one embodiment, the application may generate a layoutthat may organize the NDT data according to its type, date received,identification number, or the like. In this manner, the expert may beprovided a comprehensive view of the NDT data available to be analyzed.In another embodiment, the application may generate a layout based onthe process described above with respect to block 3374 of FIG. 19.

In addition to or lieu of generating the layout, the application mayimport a set of data analysis tools based on the user identificationinformation. That is, the application may determine the set of dataanalysis tools that may be defined as a preference for the user.Alternatively, the set of data analysis tools may be generated orimported according to the process described above with respect to block386 of FIG. 20.

After generating and displaying the layout and/or the data analysistools, the application may, at block 396, receive a request orindication from the expert to analyze NDT data. As such, the expert mayprovide an input to the application using an input device that mayindicate a particular set of NDT data to be analyzed. At block 398, theapplication may implement a user workflow that may be used to analyze orreview the selected NDT data.

The user workflow may be determined based on a template that may beaccessible by the cloud 24. The cloud 24 may have access to a number ofuser workflows and the application may display each user workflow to theexpert. The expert may then select a user workflow to use to analyze theNDT data. In certain embodiments, the user workflow may have beencreated by the expert using an application-building tool that may bedesigned to create a data analysis workflow to review and analyze theNDT data.

Alternatively, the user workflow may be imported via the NDT data. Thatis, the application may use a particular user workflow for each type ofNDT data, and the user workflow may be defined in the metadata of theNDT data. For example, the NDT data may have been acquired using aparticular inspection workflow that may have assisted the NDT inspector276 in performing his inspection. The inspection workflow may have beengenerated by an expert or the like using an application-building tool todefine a process in which an inspection in the NDT system 10 may beperformed. The inspection workflow may be associated with a particularuser workflow that may be used to analyze the NDT data. In this case,the metadata of the acquired NDT data may indicate that the NDT data wasacquired using the particular inspection workflow and may also indicatethe association between the particular inspection workflow and therespective user workflow.

Keeping this in mind, the user workflow may be a part of an overallworkflow definition along with the inspection workflow. As such, incertain embodiments, the overall workflow definition may be sent to anNDT inspection device 12. The NDT inspector 276 may then access theinspection workflow via the NDT inspection device 12 to guide himthrough his inspection process. As the NDT data is acquired by the NDTinspection device 12, the NDT data may be modified to include metadatathat defines the overall workflow, including the inspection workflow andthe user workflow that may be used to analyze the acquired NDT data.When the NDT data is accessed later by an expert or the like for reviewand/or analysis, the application may access the metadata of the NDT datato determine an appropriate user workflow to implement for the reviewand/or analysis of the NDT data. As mentioned above, the user workflowmay specify a layout in which to display the NDT data, a set of dataanalysis tools, pre-configuration algorithms, and the like.

After the NDT data has been analyzed and/or reviewed, the applicationmay generate a report that may summarize the analyzed NDT data. Thereport may also include a summary of the user workflow implemented whenanalyzing the particular NDT data, a summary of the inspection workflowused to acquire the particular NDT data, or the like. The report mayinclude modified versions of the NDT data at different stages in theworkflow. After generating the report, the application may send thereport to one or more individuals or to the database 272. The recipientsof the report may be specified by the user of the application, withinthe workflow, or the like.

Technical effects of the systems and techniques described herein includeautomatically offloading NDT data from NDT inspection devices to anothermachine for storage and further analysis. In this manner, the NDT datamay be analyzed more efficiently using additional processing power thatmay be provided by the other machine. Moreover, the NDT data may beanalyzed more effectively since it may be analyzed with respect to othersimilar NDT data.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

The invention claimed is:
 1. A collaboration system, comprising: anon-destructive testing (NDT) inspection device configured tocommunicate with at least one other computing device via a computingnetwork, wherein the computing network is configured to communicativelycouple a plurality of computing devices and wherein the NDT inspectiondevice is configured to: acquire inspection data; establish acommunication connection to the at least one other computing device;continuously send the data to the at least one other computing device,wherein the at least one other computing device is configured to analyzethe data; and receive the analyzed data from the at least one othercomputing device.
 2. The collaboration system of claim 1, wherein theinspection data comprises raw data.
 3. The collaboration system of claim2, wherein the raw data comprises ultrasound data, eddy currentinspection data, radiography data, image data, video data, audio data,or any combination thereof.
 4. The collaboration system of claim 1,wherein the NDT inspection device is configured to send an indication ofone or more algorithms to the at least one other computing device,wherein the data is analyzed by the at least one other computing deviceusing the one or more algorithms.
 5. The collaboration system of claim1, wherein the at least one other computing device is a cloud computingnetwork comprising one or more processors configured to analyze thedata.
 6. The collaboration system of claim 1, wherein the at least oneother computing device is a server, a desktop, a laptop, a mobiledevice, or a combination thereof, comprising one or more processorsconfigured to analyze the data.
 7. The collaboration system of claim 1,wherein the at least one other computing device is configured to performone or more iterations of data analysis on the data, and to transmitresults of each iteration to the NDT device.
 8. The collaboration systemof claim 1, wherein the at least one other computing device isconfigured to analyze the data as it is received.
 9. The collaborationsystem of claim 1, wherein the NDT inspection device is configured toreceive one or more reports from the at least one other computingdevice, wherein the one or more reports are generated based on theanalyzed data.
 10. A computing device comprising program instructionsconfigured to: receive data that has been acquired using one or morenon-destructive testing (NDT) inspection devices; identify metadataassociated with the data, wherein the metadata comprises informationthat corresponds to an asset being inspected using the one or more NDTinspection devices; organize the data based on the metadata; and storethe organized data in a memory.
 11. The device of claim 10, wherein theinformation comprises one or more methods and/or inspection protocolsbeing used to inspect the asset, one or more measurements associatedwith the asset, one or more component identifications that may be partof the asset, or any combination thereof.
 12. The device of claim 10,wherein the organized data is stored on the computing device, a databaseconfigured to couple to the computing device via a computing network, orany combination thereof.
 13. The device of claim 10, wherein the data isorganized based on a respective fleet in which the asset is associatedwith.
 14. The device of claim 10, wherein the program instructions areconfigured to modify the received data such that a provider of the datais anonymous.
 15. The device of claim 10, wherein the programinstructions are configured to analyze the organized data to determineone or more trends associated with the asset, operational lifeinformation associated with the asset, maximum and minimum parametersassociated with the asset, or any combination thereof.
 16. Anon-transitory computer readable storage medium comprising instructionsconfigured to: receive signals from one or more inspection sensors asraw data; transmit the raw data at a first time to one or more computingdevices for a data analysis, wherein the raw data is analyzed usingautomatic defect recognition technology; and receive the data analysisfrom the one or more computing devices at a second time.
 17. Thenon-transitory computer readable storage medium of claim 16, wherein theone or more computing devices comprises a cloud computing networkcomprising one or more processors configured to analyze the raw data.18. The non-transitory computer readable storage medium of claim 16,wherein a difference between the second time and the first time is lessthan between 1 second and 1 minute.
 19. The non-transitory computerreadable storage medium of claim 16, wherein the raw data is analyzedusing one or more data analysis tools configured to analyze the data forone or more measurements associated with an asset being inspected by theone or more NDT inspection devices, assisted defect recognition in theasset, disposition information on the asset, and any combinationthereof.
 20. The non-transitory computer readable storage medium ofclaim 16, wherein the raw data comprises ultrasound data, eddy currentinspection data, radiography data, image data, video data, audio data,or any combination thereof.